QA as a sub-project: draft 'governance' section for the wiki

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey, folks.

So here's some funny Fedora archaeology: QA is not actually officially a
Fedora sub-project. I didn't know this (and didn't particularly care!),
and neither did I know that, aeons ago (well, last year), jlaska kicked
off an attempt to make us one. As sub-project requests are filed as
Board trac tickets, I can't link to it because of the Board's silly
policy of making trac tickets private, so only they and jlaska can see
it. But I'm assured it exists. If anyone is super-interested in this
exciting, nay thrilling process, it's documented at
https://fedoraproject.org/wiki/DefiningProjects#Fedora_Projects .

Anyway, Robyn tells me that with its customary, legendary efficiency and
speed, the Board has come to a swift decision a mere eight months later
that QA should be accepted as a sub-project.

Robyn also requested that we have our 'goals' written down somewhere,
and that we have some kind of section on leadership/governance.

I'd say the line "It's our goal to continually improve the quality of
Fedora releases and updates" on the front page of the wiki, plus the
'Activities' section below, pretty much covers goals. As far as
leadership / governance goes, I propose adding the following to the wiki
somewhere, I guess the front page (though I really want to keep that
short and, um, free of silly bureaucracy, so if anyone can think of
anywhere else...)

== Governance ==

The QA project does not have a formal governance structure.
Decision-making is done by broad consensus and peer review, a mechanism
which has worked successfully for many years. There is no single leader
of the QA project. Significant decisions will be taken by implied or
explicit vote on the project mailing list, in the project meeting, or in
a project trac ticket relevant to the issue at hand. Any issue requiring
the QA team's input should be brought up on the project mailing list or
at a project meeting, or filed as a project trac ticket.

That's just off the top of my head, obviously. Amendments /
improvements / shortening (especially shortening!) welcome. Let's use
consensus to produce the statement that we do things by consensus. ;)
I'm not sure if it's worth specifically calling out that probably the
most important recurring decision that's our responsibility - signing
off on releases - is taken according to strict deterministic rules (see
https://fedoraproject.org/wiki/Go_No_Go_Meeting ).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux