Roy,
This piling on behavior seems to have come from the notion that if you get
on the initial vote, you're in, but otherwise you have to earn
committership. And the justification for the first part seemed to be making
sure that a company could not start with a lot of its own people, and keep
out existing ASF committers and other interested parties.
My long standing proposed solution for this is embedded in my description of
project startup:
- bootstrap the PPMC from the PMC (assigning Mentors)
- election by the PPMC of project contributors to the PPMC
- election by the PPMC of Committers
So the Mentors first task is to formally bring on board the key outside
players, and then that PPMC elects Committers, both to start and going
foward. This addresses your point that:
> Podlings must be open to new contributors and should add contributors
> to the list of committers fairly quickly, at least when compared to
> more established Apache projects. However, the core team must be
> allowed to select other core members based on mutual consensus,
> since consensus is how code changes are approved. How a community
> exercises that consensus is one of the primary determinants for
> graduation.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
