On 2/1/02 10:55 PM, "Steve Downey" <[EMAIL PROTECTED]> wrote:
> http://jakarta.apache.org/site/decisions.html > > My understanding of Apache voting rules is that every commit is a change to > the product. It's subject to lazy consensus. Which means if no one objects, > it's OK. If someone issues a binding -1's to a patch or commit, it must be > reverted. This I understand. What I don't understand is how we would separate the two - if we had everyone be able to commit, but only some people could vote... geir > > q.v. http://httpd.apache.org/dev/guidelines.html, also. > >> -----Original Message----- >> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] >> Sent: Friday, February 01, 2002 6:48 PM >> To: Jakarta Commons Developers List >> Subject: Re: Voting Rights >> >> >> On 2/1/02 6:39 PM, "Scott Sanders" <[EMAIL PROTECTED]> wrote: >> >>> So, how do we make voting rights separate from commit rights? >> >> I am interested in understanding the difference. If I can >> commit anything I >> want to the codebase, why do I care about voting rights? Or >> is every commit >> examined and voted on? >> >> I think that the conventional apache approach of making them >> one in the same >> results in the solution to the problem. >> >> We can solve the issue of ensuring that people can have a >> place to work and >> experiement via the sandbox. >> >> >>> Do we ammend the charter to state how? >>> >>> Scott >>> >>> -- >>> To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> >> -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting POC lives! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
