Category:Documentation beats

Beat Assignments

This page lists all of the writing beats for the release notes, and who is assigned to them. See an empty slot? That means it's waiting for you! More specifically...

What will I be writing?

Beat writing is a good place for a new contributor to start working with the Fedora project. You'll learn about the next release of Fedora, but you don't need to be highly technical. Most of the work is done in the wiki, which means it's easy to get input from more experienced contributors.

These beats are essentially draft sections for the release notes document. (An annotated version of the Fedora 25 schedule for Release Notes is available at Releases/25/Schedule.) You're likely to have a developer contact and will be able to use the feature pages for your beat, as well as other resources. You can even start by pasting the release notes from your feature's page. So don't be nervous--just claim a beat!

Review Docs_Project_workflow_-_beat_writing for more thorough details about what you'll need to do.

How to take a beat or remove yourself from one

- If a beat writer has an asterisk (*) next to his/her name, that writer has not yet indicated whether (s)he will write for Fedora 25. If you are that writer, and you are still willing to help, please remove the asterisk.

- If a beat is a lonely orphan with no writer, and you'd like to be that person (or to help), just add your name to the Writer column.

- Once you've added your name, you should subscribe to the content flow mailing list.

Beat Closed on Wiki
Work on beats has now moved to git at https://pagure.io/fedora-docs/release-notes. If you have changes or additions, please contact the docs team via #fedora-docs, docs@lists.fedoraproject.org, or with the release-notes BZ component.

Welcome to Fedora 25

Installation Notes

Architecture Specific Notes

Changes in Fedora for Desktop users

Changes in Fedora for System Administrators

Changes in Fedora for developers

Changes in Fedora for specific audiences

Appendices

Status key:

• A 1 in the Wiki Good column indicates that the beat is ready for conversion to XML
• A 0: Not ready for conversion to XML
• A 0 indicates that the XML needs to be backported to the wiki
• A *: Means ... what? It is recommended by "Warning / Beat Converted" blurbage.

• A 1 in the In Publican column indicates that the beat has been converted
• A 0 in the In Publican column indicates that the beat has not been completely converted to XML

• A 1 in the Proofread column indicates that the published chapter has been reviewed
• A 0 in the Proofread column indicates that it has not