| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
|- | |- | ||
! Meetings | ! Meetings | ||
| Weekly at {{fpchat|#fedora-meeting}} | | Weekly at {{fpchat|#fedora-meeting}}<BR>[[Docs_Project_meetings|Meeting Time]]<BR>[[Docs_Project_meetings#Agenda_for_Next_Meeting|Next Meeting Agenda]] | ||
|- | |- | ||
! Current issues | ! Current issues | ||
Latest revision as of 18:03, 12 March 2012
Project details
| IRC Channel | #fedora-docs[?] |
|---|---|
| Mailing List | docs-qa |
| Meetings | Weekly at #fedora-meeting[?] Meeting Time Next Meeting Agenda |
| Current issues | Fedora Documentation Bugs - Reported issues with Official Documentation |
| Project planning | Guide Listing |
| Published documentation | https://docs.fedoraproject.org |
| Related pages |
|
What is Docs QA?
Docs QA is a team of people who are working to review Fedora documentation for both accuracy and safety. The goal is to insure that the documentation that accompanies Fedora is as well polished as the product itself.
How to Help
There are two paths you can take in order to help. The first is to sign up to be a QA contact on the table guide, this means that you want to be the point of contact on that guide. You are responsible for working with the Guide Lead to insure that new content is check and that the guide is scrubbed for outdated information before each release.
The second way to help out to simply review content. Find out what needs a set of eyes, either in #fedora-docs or the docs mailing list, and jump in. After you check the content let the QA contact for that guide know that you have looked it over and that you found nothing, or file a bug (or identify in the current bug) what you found wrong.
Ideas
+ QA Day or Week: A time frame before Docs go to trans that we make a big push to verify docs for release.