-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
A while back we discussed putting together a group of editors that would review changes and guides to make sure they were correct and written well. Since then little has happened. The biggest issue has been extra cycles in peoples' day and I can appreciate that. This is an important task that anyone with a little time can help out with. It's especially good for newbies that want to become involved but aren't familiar with DocBook and the like as they can see what we are writing and *how* we are writing.
With that said, I'd like to propose the following:
1) We change the QA on all components in BZ to docs-qa(a)l.fp.o so interested QAers can subscribe to that list and see when QA is needed. We also need to setup docs-qa in BZ and maybe have it send a message only when the the ticket is set to MODIFIED and ON_QA (I think this is possible).
2) Create a wiki page outlining the purpose and mission of docs-qa and provide guidelines for what to check for.
3) Create a wiki page outlining the guidelines for QA in the bug-handling process.
Thoughts?
- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iF4EAREIAAYFAk2Y38cACgkQU03aaJDMNEUHewD/SQZbVNfwXFNId48nkeEw1VCR
F1M3emNRYTtrKfk9pKIA/1p56T+fNpmoi3gUGWwZQOO/oOQXzltOkW4wAY7efSQC
=SVzt
-----END PGP SIGNATURE-----
