On Thu, Nov 11, 2010 at 6:56 PM, Eric "Sparks" Christensen <sparks@xxxxxxxxxxxxxxxxx> wrote: > For the QA goal, I foresee all changes to guides being put in front of > an editor/fact checker to make sure that what we are saying is correct > and that the procedures are correct (and most importantly won't bork > someone's system). The QA process can be integrated into Bugzilla (it's > actually already there) and we can keep track of changes in that manner. > > Anyone have any thoughts? We should get some time lines together for QA and add them to the schedule, during the last release, checks started late on at least one doc and caused it to miss set publication time lines. We need to sit down and figure out what the schedule should be, but some docs are much longer then others so we need to have a good buffer built in. I think that we should also add a QA contact to the guides table [1], making that person over all responsible for making sure that the doc gets checked. I am not saying that person has to do all the work, but we need to have some kind of oversight on it. [1]: https://fedoraproject.org/wiki/Docs_Project_meetings#Guides -- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
