Hi, > "Lazy Majority" and "Lazy 2/3 Majority" just doesn't make sense to me. These are exactly as most other Apache projects including HTTP (it doesn't mention 23rd majority however).
From http://httpd.apache.org/dev/guidelines.html. "An action item requiringmajority approval must receive at least 3 binding +1 votes and more +1 votes than -1 votes" "Lazy majority decides each issue in the release plan." See here: http://ant.apache.org/bylaws.html https://cwiki.apache.org/confluence/display/KAFKA/Bylaws http://hadoop.apache.org/bylaws.html http://pig.apache.org/bylaws.html https://cwiki.apache.org/confluence/display/Hive/Bylaws https://cloudstack.apache.org/bylaws.html http://wiki.apache.org/jclouds/Bylaws And probably others (just a quick search). There a little variation on if it called "Lazy Majority" or "Majority Approval" but the rules are the same. (Note Hive is a little different as it make a distinction between "Lazy Majority" and "Lazy Approval" and "Lazy Consensus".) And also here: http://www.apache.org/dev/release.html http://www.apache.org/foundation/glossary.html#ConsensusApproval http://www.apache.org/foundation/glossary.html#MajorityApproval Rules are the same but refers to it in the glossary as Majority Approval. "Votes on whether a package is ready to be released use majority approval -- i.e., at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed." "Refers to a vote (sense 1) which has completed with at least three binding +1 votes and more +1 votes than -1 votes. ( I.e. , a simple majority with a minimum quorum of three positive votes.) Note that in votes requiring majority approval a -1 vote is simply a vote against, not a veto. " > The HTTP guidelines sort of explain something like that as "Lazy approval" > until someone votes -1..." That's lazy censuses not majority. > Otherwise, as soon as someone votes -1, everyone who had silently > consented and moved on to something else now has to keep tabs on the vote > and see that and then vote. Encourages people to vote and have a say IMO and the person who raised the vote to encourage other people to vote - just like a release. The only common action that require Majority voting are releases. I guess the the guidelines may change occasionally (2/3 Majority). I hope we don't have the situation where we have to vote on removal of PMC or committer members that often. > Minor nit: In "Code Change" I think "any" is missing in this portion: > "-1 vote by other committer" Changed. I think that can be considered a very minor change and not require a new RC - especially given that no one has actually voted yet. Thanks, Justin
