non-coding sub-projects

[Karsten 'quaid' Wade]

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

On 07/09/2012 11:15 PM, Itamar Heim wrote:

>> there is no connection between being a maintainer in a sub
>> project and joining the board.

I was forgetting that the project leads who were made part of the
initial Board was not the norm:

"A few domain leaders from projects. Not all projects have board
representation so that community members can work to fill some of
these seats related to projects. Not every project has to be on the
board. They do however need to participate in the coordination mail
lists."

http://www.ovirt.org/governance/board/

However, there is a meaningful connection. Becoming a maintainer is a
sign of individual merit, and a collection of such merit is a
prerequisite to being voted on to the Board.

Similarly, a project is likely to appreciate having one or more
maintainers who are Board members. As a hard development project,
infrastructure is more strategic to us than to other open source
projects. So in Infrastructure's case, there is value in having one or
more maintainers able to get on to the Board so they are helping
influence the project direction.

>> we already have the non coding documentation project by stephen
>> gordon, though missing from that wiki i guess as an oversight

I missed the discussion around adding that as a project, sorry. What
was the decision criteria? Is the process in a document somewhere? I'd
like to update the
http://www.ovirt.org/governance/adding-a-subproject/ page.

- - karsten
- -- 
Karsten 'quaid' Wade, Sr. Analyst - Community Growth
http://TheOpenSourceWay.org  .^\  http://community.redhat.com
@quaid (identi.ca/twitter/IRC)  \v'  gpg: AD0E0C41


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

iD8DBQFP/IEi2ZIOBq0ODEERAq8FAKDCwzYjYMe4Hotqy/UB1B8Kzz8S0gCgpN56
+QbhEPZXX0knz6LXZG4EEHQ=
=Tqod
-----END PGP SIGNATURE-----