Hello Fedora, The Fedora 22 release cycle is in full swing, and beats have been opened for the F22 Releasae Notes. Over the coming weeks, the release notes for the next version of Fedora will be assembled by Docs team writers, packageers, developers, and community members of all forms. Yeah, that's a pretty broad group. You can help - not a figurative, abstract "you", but you, reader, can personally contribute to this fine periodical publication. Not a technical writer? That's OK! The most difficult part is the initial prep and research, and that's where we can use you the most. Here are some examples of ways you could contribute: - You maintain a package, and are able to update it to the next major version for F23. The new version has some long-awaited features added that users would enjoy. To signal the Docs team to write a bit about these changes, you open the release monitoring bugzilla ticket and check the "fedora_requires_release_note" flag. We can take it from there, but please be available for follow up questions! - You subscribe to a mailing list (one? who is this guy?) and a discussion reveals some notable change in a component of Fedora. While mailing lists are discoverable, the archives aren't one's first stop, so you forward the thread to a dedicated mailing list, "relnotes-content@xxxxxxxxxxxxxxxxxxxxxxx". Like all Fedora's lists, you must subscribe to send - but don't worry, we'll watch the approval queue. - As a contributor to Fedora QA, you are were one of the earliest adopters of Fedora 23 as a daily driver. While testing packages and generally going about your business, you find that something has changed; the syntax or location of a config file, perhaps, or maybe the user experience of your favorite media player. Drop a note into the wiki at https://fedoraproject.org/wiki/Category:Documentation_beats and some writers will come along to write the prose and share it with the world. - You're an active member of a SIG. There are some exciting changes and additions to the packages supported by your SIG. It could be a new skychart from Astronomy, or a new mapping client from GIS, or new applications and features on the XFCE spin. You drop in to #fedora-docs on Freenode to hash it out with the Docs team (there's almost always someone there, but you might have to wait a bit for the first reply.) I'm getting long-winded now, but there's one point I want to stress. Note that none of these options said anything like "Write comprehensive, gramatically correct documentation in American English that is ready for publication." If you want to participate to that degree, great! If not, don't be dissuaded. It's a huge help to have leads and requests thrown into the funnel, there are writers waiting to take it the rest of the way. -- -- Pete Travis - Fedora Docs Project Leader - 'randomuser' on freenode - immanetize@xxxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ test-announce mailing list test-announce@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/test-announce
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
