Commit Digest/Editor guidelines: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
* In the synopsis, most important items go first, moves / deletions / tagging / releases / miscellaneous at bottom. Also, try and group items where they make sense (eg. mentions of KOffice stuff can be followed by Calligra / Skrooge / etc items) | * In the synopsis, most important items go first, moves / deletions / tagging / releases / miscellaneous at bottom. Also, try and group items where they make sense (eg. mentions of KOffice stuff can be followed by Calligra / Skrooge / etc items) | ||
* In the introduction line to feature articles: the first mention of a program should be hyperlinked to the project site (e.g. <a href="http://koffice.org/">KOffice</a>) | * In the introduction line to feature articles: the first mention of a program should be hyperlinked to the project site (e.g. <a href="http://koffice.org/">KOffice</a>) | ||
* In any mentions, always either '''KDE Commit-Digest''', '''Commit-Digest''', or '''Digest''' (note the capitalisation and hyphenation) | * In any mentions of the publication, always either '''KDE Commit-Digest''', '''Commit-Digest''', or '''Digest''' (note the capitalisation and hyphenation) | ||
Revision as of 23:38, 23 February 2011
- In the synopsis, most important items go first, moves / deletions / tagging / releases / miscellaneous at bottom. Also, try and group items where they make sense (eg. mentions of KOffice stuff can be followed by Calligra / Skrooge / etc items)
- In the introduction line to feature articles: the first mention of a program should be hyperlinked to the project site (e.g. <a href="http://koffice.org/">KOffice</a>)
- In any mentions of the publication, always either KDE Commit-Digest, Commit-Digest, or Digest (note the capitalisation and hyphenation)