m (Robot: Changing Category:DocsProject) |
|||
| Line 98: | Line 98: | ||
| [[Docs/Beats/Networking| Networking]] || [[ThomasGraf]] || [[ChristopherAillon]] | | [[Docs/Beats/Networking| Networking]] || [[ThomasGraf]] || [[ChristopherAillon]] | ||
|- | |- | ||
| [[Docs/Beats/Virtualization| Virtualization]] || [[ | | [[Docs/Beats/Virtualization| Virtualization]] || [[JasonTaylor]] || ''Open'' | ||
|- | |- | ||
| [[Docs/Beats/Xorg| Xorg]] (X Window System) || [[BobJensen]] || [[AdamJackson]] | | [[Docs/Beats/Xorg| Xorg]] (X Window System) || [[BobJensen]] || [[AdamJackson]] | ||
Revision as of 18:08, 18 July 2008
Release Notes Beats
Where the Beats are Written
Come help cover the relnotes beats at Docs/Beats .
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
This page lists all of the writing beats for the release notes, and who is assigned to them.