Leo Simons wrote: > >> Since committing is voting, what I think what some people want is a >> non-vetoing Committer. > > I think 'some people' don't see/don't agree to the "committing is > voting", and then what they want is a Developer-with-CVS-access, which > is more or less what they said. > > "Committing is voting" is not reflected in our guidelines (at least I > couldn't find such a notion).
In projects like <http://httpd.apache.org/dev/guidelines.html>, any impleementation of an idea (as opposed to a simple patch) must be review-then-comment. In most Jakarta subprojects, the norm is lazy consensus as defined in <http://jakarta.apache.org/site/decisions.html>. So, think of a commit as the first (any typically only) +1 most changes get. >> Someone to do the work without sharing in the >> responsibility. > > sounds like what we call "developer" in our guidelines ;) A "developer" can suggest a change. A "committer" can make it happen. - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>