Jason van Zyl wrote:
People get voted on to the PMC by other PMC members. Being a committer
doesn't automatically get you on the PMC in these parts. I'm
personally not for the free-for-all access to everything. I don't
honestly understand why there is any distinction between a committer
and PMC member in Cocoon if it's always the same thing. Committers are
people who code and contribute, while PMC members are helping to
direct the project.
Some Cocoon committers choose not to join the PMC. I'm not really sure
why. And I don't really understand your distinction as it implies that
some PMC members don't code or contribute but yet help direct the
project. I'm not sure why someone who codes and contributes can't help
direct the project (in fact, they do since every source code change they
commit changes the project).
Generally, the PMC only offers commit privileges to people who actively
participate on the mailing lists by helping others and who have either
submitted patches (and thus can document their knowledge in how Cocoon
works) or by working on the documentation. Some people have been on the
Cocoon mailing lists for years and haven't been offered commit
privileges while others have it offered after several months. In
general though, by the time they are offered commit privileges the PMC
has a pretty good idea of their desire to participate in the community
and their ability to do so, so at that point we feel being a PMC member
is appropriate.
BTW, I'm not trying to say one way of doing things is better than the
other. Obviously, both communities seem to be pretty healthy. I'm
simply trying to understand what criteria you use when you offer PMC
membership.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
