Non-binding +1.
On Wed, Nov 12, 2008 at 7:47 AM, Grant Ingersoll <[EMAIL PROTECTED]> wrote: > Seems reasonable on the committer front. Of course, one person's trivial > bug isn't always another person's trivial bug, but, hey, that's what > rollback is for, right? > > As for the PMC issue, it may be problematic in the long run if Droids > becomes a subproject of a TLP. For instance, in Lucene, not all committers > are PMC members and I highly doubt the PMC would vote to add every Droids > PPMC member in as a Lucene PMC member. That being said, we still pretty > much treat committer's votes as binding, although it rarely is an issue. I > can't remember there ever being an issue where a PMC member had to play that > trump card. > > -Grant > > > On Nov 12, 2008, at 3:35 AM, Thorsten Scherler wrote: > >> Hi all, >> >> I always said I would like to maintain the commit access for all ASF >> committer when leaving labs. I had a chat with Grant et al. about it >> @apacheCon. >> >> The problematic part was pointed out to me that if we give everybody >> commit access we run the danger that asf committer to droids can make >> contra-productive committs without going to the issue filter. IMO we can >> state in our project guidelines (on which we need to work) that trivial >> changes can be committed without prior discussion but any deeper >> architectural changes have to be discussed in the dev list and best >> demonstrated with a patch attached to our issue tracker. If we agree we >> should add the ASF committer group to our trunk svn policy file. >> >> The other thing is becoming part of the PPMC. I am PMC member on >> different PMC's and every project has its own policy on this matter. I >> personally like best the one from forrest. Every committer is part of >> the PMC since IMO if you are committed to the project you should have as >> well a binding vote. >> >> I would like to propose the following policy around commit and PMC >> access here @droids: >> "All ASF committer have write access to the public svn source. We >> encourage all ASF committers to fix trivial bugs (like typos, etc.) >> without prior consultation. However bigger changes (like architecture >> changes and major code rewrites) HAVE TO be discussed prior on the dev >> list and best demonstrated with a patch attached to our issue tracker. >> >> Every ASF committer that has demonstrated his/her commitment to droids >> through the normal meritocracy policy we have on the ASF will be voted >> in from all active PMC members. >> >> New droids developer (non-ASF committers) are need to demonstrate >> his/her commitment through the normal meritocracy policy we have on the >> ASF. If they get voted in as committer their should as well become part >> of the PMC since if they are committed to the project they should have >> as well a binding vote." >> >> WDYT? >> >> salu2 >> -- >> Thorsten Scherler <thorsten.at.apache.org> >> Open Source Java <consulting, training and solutions> >> >> Sociedad Andaluza para el Desarrollo de la Sociedad >> de la Información, S.A.U. (SADESI) >> >> > >
