> 3) Limit the number of new non-ASF initial committers for incubating projects > People who were not ASF committers but come in via a newly incubating > project do not get their commit rights via the normal ASF meritocracy > rules. > > We might want to limit the number of such commiters, to limit the > number of people who get in via this "shortcut". > > The downside of such a limitation, as someone mentioned in > discussions, is that getting new committers in this way is also an > opportunity to "convert" more people to the ASF way.
If I think about Wicket, this limitation would have been a problem, since at the time Wicket started incubation, only one of the team members (of the 10+) was already involved an ASF committer. I'm not sure what benefits such a rule would have. True, you don't have much insight in how people of incubating projects got into the project before incubation, but on the other hand, it shouldn't really matter as the incubation is meant for coaching the project members into the ASF way, or at least validating that they can behave in the ASF way for the ASF projects concerned. I believe this should be viewed entirely independent of what they do or have done in outside projects. In other words, I believe ASF should only be concerned about how ASF projects are affected. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
