(fix double redirect) |
|||
| Line 5: | Line 5: | ||
== Where the Beats are Written == | == Where the Beats are Written == | ||
Come help cover the relnotes beats at [[Category:Documentation beats|the beats page]] . | Come help cover the relnotes beats at [[:Category:Documentation beats|the beats page]] . | ||
Beat writers must be subscribed to the [http://www.redhat.com/mailman/listinfo/fedora-relnotes-content content flow] mailing list. | Beat writers must be subscribed to the [http://www.redhat.com/mailman/listinfo/fedora-relnotes-content content flow] mailing list. | ||
Revision as of 13:37, 21 April 2010
Release Notes Beats
Where the Beats are Written
Come help cover the relnotes beats at the beats page .
Beat writers must be subscribed to the content flow mailing list.
What is a Beat?
A beat for a writer is a fixed area that you write about. For journalists, covering the proceedings of the local city council is a beat, as would the writer covering the local sporting events.
For the Fedora release notes, a beat covers an area of the release. This puts writers who are interested in a topic in direct contact with the developers of the software. Developers get to know who is their writer, and can send over information knowing it will be documented, visible, and highly available.
More information on the process is available at
http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process
Filing A Release Note Request
If you are looking to file a release note, please use this pre-filled bugzilla template . If you want to know more about writing for the Documentation Project, refer to ["DocsProject/NewWriters"] .
To check release note bugs, check bugzilla .
The release notes are available online with the rest of Fedora documentation.
Beat Assignments
A list of current beats and their writers can be found here