On Tue, Nov 05, 2002 at 07:33:37PM -0800, Costin Manolache wrote:
I think more details on 'veto' validity are needed - we had a lot
of problems in this issue. Like the second opinion.
It should also include some mention on release and codebase
decisions ( i.e. majority vote for releases, and clarification
on the 'revolution' rules ).
Actually, is it majority or lazy consensus for releases? Over in HTTPD
we do a lazy concensus where
- releases can not be vetoed
- there must be at least 3 +1s
- there must be more +1s than -1s (simple majority)
- (also, unfortunately, I believe these votes must come from the PMC)
I don't know if the 'revolution' rule is specific to jakarta
or is implied by the 'majority takes the name' - but by definition
a revolution can go over a veto ( otherwise it won't be a majority,
but one person that can make this kind of decisions ).
What is this 'revolution' rule I hear of so often? Is there a document
out there or something that I can read?