Project goals for F15

Eric "Sparks" Christensen sparks at fedoraproject.org
Fri Nov 12 13:50:37 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/12/2010 02:14 AM, Zach Oglesby wrote:
> On Thu, Nov 11, 2010 at 6:56 PM, Eric "Sparks" Christensen
> <sparks at fedoraproject.org> 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

Agreed.  We should get Robyn in on modifying the schedule a bit for F15.
 I think RH has a figure for how long it takes to QA a guide based on
the number of pages.  My thought is that if we keep all the changes on
BZ and only commit the patches once they have been approved by the QA
person then we could cut down on the amount of time it should take to do
the work.  Especially when you can look at the patch and see what was
changed (if you know the base was correct in the first place).

QA people can be assigned to each BZ product to automatically get the
tickets so all I need to do is figure out who wants to do what guides
and I can put that into BZ.

- --Eric

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJM3UYsAAoJEDbiLlqcYamx6c4P/iLLlDiwIHey0+8wK+Te2oVR
U2Hw6amvaKbTx2KBLdOzUmjWBgVa0+uXODwUOUn33UyJCY/gdxW4jdfTCIDbePcn
vN/vzWtv0ap5W/2AYcnFIh5bQPfEQ6teO2SGFz+toNL6/xZ3t9nVfaHe1V/CaEvF
dqHph8iGBkqBjh5WHglEFNz6Hg/eJbLtV+hLl9DG23NlVgu5hHkEppp2NHCGugri
k6MA18eVjLoip4lYhkw5tJPHDjFtOp15Ek3dp1/L3MbkOAWsYYHgQI5YeiC/0fAk
E89oPJUGeGHOhaCZoit0s7MzFPAVNbddwRxNVe2vqkB0q+asIFtyGnkjUeYYbBJr
bCq7NozJtbkMv2XLiRqKgEf8nHn3M3q3I4sVPbM3LnS0iCO1ToUjVkgBcH0sBbKV
vHpsZXGku1SK/2xrAgf/7JB+9OoVS07GQyYqjswDmTDiSLJM2oj/7hPE+5+4wGUt
WdyM/XdslubaeHuHqtGQYbwqevLxFacmGqMIA7V09yAO66zIgKDE9kQRiAL7iJyP
rYZeojO33s2FI5jcoBCXl7TUb17nM27oJUPOYXzZ9KEVDqqxIU115ITJBxvGe8MH
2MheGDKpudHyiEQor6uJdifn/xbRbQHjOTiHLzNrXecfgR8t5WVDB//USOvZ3zQ+
+d6aIoK2nQlhFwuRHry6
=9k/0
-----END PGP SIGNATURE-----


More information about the docs mailing list