This discussion is way out of hand. It has become totally unclear what is even under discussion any more.
The project was approved with a certain committer list. What more can be said? The project was approved, the committer list was part of the project proposal, hence everyone on the list should be committers. It could not be more straightforward. Apache is about merit, transparency, etc. Some guys had a con-call and private emails and decided to void the project proposal after it was approved? To me that doesn't make any sense at all. That sounds like the exact opposite of how the Apache process has been described. Not to flame, apologies have been made and it was an honest mistake. (Or something...I'm not sure anyone really understands the situation entirely) The more general issue of having "too many" committers I don't understand either. If a company has 15 employees working on a project then yes, they will dominate the discussion. If all 15 people are actually contributing that is the way it *should* be. More contributers is a good thing right? If out of those 15 people only half are actively committing the other half should have their commit privs revoked. To me aggressively weeding out those who don't really commit is a lot more straightforward than trying to divine in advance who is really going to be contributing or not. If the source comes from a company and was originally closed-source how is anyone going to find out who worked on it or not anyway? It is difficult if not impossible to figure out who has contributed to a closed-source project, but it is quite easy to figure out who is actively committing after a project is accepted and a couple of months have passed. Again, if everyone on the list of original committers actually commits and contributes there is no problem, no matter how large the initial list is. It's only a problem when people on the initial list don't actually contribute after the project is accepted, which is easy to detect. So I would say if you make it easy to revoke committer privs these problems are self-correcting. If they can be easily revoked due to inactivity then the original list doesn't really matter too much anymore, as it would only be binding for a few months. That seems straightforward and in line with the Apache approach. In short, commit access is a priveledge, use it or lose it. Just my two cents as a lurker/observer. James Margaris -----Original Message----- From: Mladen Turk [mailto:[EMAIL PROTECTED] Sent: Monday, October 02, 2006 1:50 PM To: general@incubator.apache.org Subject: Re: Policy on Initial Committership I was against that project from start, because some members proposed as commiters were bitching ASF for years. Now, it seems that even inside that project there are some irregularities that do not follow the ASF rules (well, at least the ASF spirit). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
