On 04/12/12 14:52, intrigeri wrote:
> Hi,
>
> sajolida@??? wrote (03 Dec 2012 21:48:33 GMT) :
>> Are we proposing them to write us about past or future
>> press releases?
>
> My idea was to propose them to (manually) "subscribe" to future press
> releases only.
>
>> Would that work?
>
>> « We also sometimes publish press releases but they are not archived on
>> the website. Write us an email at <tails@???> if you want to
>> receive our previous press releases or be informed of future ones. »
>
> Great. Without the past ones, that would result in:
>
> « We also sometimes publish press releases but they are not archived on
> the website. Write us an email at <tails@???> if you want to
> be informed of future press releases. »
>
> Suits me well.
Ok, done in commit b1c260d.
>> Ah, and about the capitalization of titles, Ague convinced me of
>> following the Wikipedia guidelines. In short "do not capitalize the
>> second or subsequent words in an article title, unless the title is a
>> proper noun."
>
> Not that I care much about which format we use for titles
> specifically, but I do care about how easy it is to know and tell what
> the rules are. As long as they were "follow the GNOME documentation
> guidelines", it looked easy enough to me to remember and re-transmit.
> But if, in practice, we're creating our own set of guidelines (like
> "we use GNOME doc guidelines modulo titles are like on WP"), then
> perhaps they should be documented. Else, I fear we're creating arcane
> knowledge of how contributions should look like. What do you think?
Damn, you right: that differs from the GDSG. But I've seen them applied
and recommended in other places (Wikipedia among others) and I've
applied them extensively so far, so I'd like to stick to that.
I've been thinking about writing documentation guidelines for a while.
Now you pointed out a good reason that made me actually do it. Please
have a look at:
https://tails.boum.org/contribute/how/documentation/guidelines
