Hi all,
We're well into the validation portion of the F24 release cycle. The Alpha release is out, freezes are in place, and we have release notes to write.
Contribution to the release notes is coordinated via the wiki, at
https://fedoraproject.org/wiki/Category:Documentation_beats . The table there shows folks that have volunteered to investigate, and write about, changes within some defined scopes. If there's an asterisk next to a name, it's because that person has not validated their participation for this cycle yet, and the 'beat' is effectively unclaimed.
While we refer to 'beat assignment', it's really just a coordination tool. You can write about any topic of interest, even if there's already a name down; the table simply tells you who to coordinate with. Look at package changelogs, packaged documentation, upstream release notes, the Change process at
https://fedoraproject.org/wiki/Releases/24/ChangeSet , upstream docs, etc to find information about a given topic. You *do* need to find topics within a given beat through some investigation; visit #fedora-docs or mail the list if you're having trouble getting started.
There are some major areas we should prioritize. Foremost, adequate coverage of the three primary deliverables, Cloud, Server, and Workstation. There are some Changes in play for each, but we should also coordinate with the working groups for these deliverables, and do some independent investigation. It is also important to review *all* the Changes, and communicate with those change owners as needed.
An entry in the release notes should:
- Say what the thing is
- Explain what the thing does
- Give the reader an idea of why they might use the thing, or what problem it would solve for them.
- Excite the reader about the new features of the thing
- Warn the reader about things they might need to do, if they used the old version of the thing and it has changed.
The table isn't structured this way, but you might also think of the beats in terms of SIGs; there's a Python SIG, Java SIG, virt folks, kernel folks, and so on. You could liason with these groups and get the scoop on their work.
Our schedule is at
https://fedorapeople.org/groups/schedule/f-24/f-24-docs-tasks.html . We are behind schedule. Edits to the wiki seem light, so I propose we hold off on closing the wiki for a couple weeks and aim to have the content ported to docbook and published to coordinate with the Beta release.
-- Pete
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx
