On 29/12/2006, at 1:50 PM, Ralph Goers wrote:
I'm a little curious. I'm a committer on a few projects and am on the Cocoon PMC. This is the first time I've every heard of a proposal for people to automatically lose their commit privileges. Although, I haven't found any rules anywhere that says you can't do it, it seems a bit odd to me.
This is just one clean up because we have a large number of people that haven't committed in 3+ years due to the changes in technology, the move to TLP, etc.
Such things have before been discussed in Jakarta, another project with large numbers of committers that have moved on.
Second, I didn't find anything that discusses just how Maven distinguishes between committers and PMC members. I know it is up to each community to decide. I'm just used to all committers also being able to be on the PMC if they want to. So how does it work here?
I think you'll find it's not a matter of "committers being on the PMC if they want to". No project to my knowledge (Cocoon included), operates that way. However, many have set the committer bar higher, to the level of the PMC membership, so both are voted on at the same time (eg, Forrest, and perhaps that's how Cocoon operates). It's one of those discussions that happens at the ASF from time to time and nobody ever agrees on which way it should be.
As we stand, we have a lower bar for committership, but a higher bar for PMC membership.
One thing to note is that the emeritus policy will bring our number of PMC members and committers much closer together, which is desirable too.
- Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
