Well, we should keep this thread focused on Groovy but your link precisely shows the problem. One exit criteria is "growing the community", and growing the community means finding new "committers", aka, people committed to the project. And The definition here of committer binds it to having write access to the repository, which has nothing to do with it IMHO.
2015-09-29 15:12 GMT+02:00 Konstantin Boudnik <[email protected]>: > On Tue, Sep 29, 2015 at 01:54PM, Russel Winder wrote: > > On Tue, 2015-09-29 at 14:49 +0300, Roman Shaposhnik wrote: > > > > > […] > > > Well said. I typically explain it to folks that at ASF, committers > > > are those > > > who have a strong commitment to the project, not git/svn commit bit > > > set. > > > > It remains a very big shame that these two words (committer and > > committer) and their associated roles (core team member and person who > > updates the mainline repository) are so conflated by the ASF rules and > > procedures. The ASF really need to unbundle these concepts if it is a > > forward looking organization. > > I don't think Apache conflates these things. From [1] > > User: is someone that uses our software..... > Developer: is a user who contributes to a project in the form of code or > documentation... > Commiter: is a developer that was given write access to the code > repository and has a signed ICLA > > [1] https://www.apache.org/foundation/how-it-works.html#roles > > Cos >
