Hi, I just read https://cwiki.apache.org/confluence/display/FLEX/Guidelines and I think allowing vetoes for most everything, as those guidelines do, is calling for trouble.
The standard Apache voting process [1] specifies vetoes for commits only. My recommendation would be to make those guidelines much simpler by keeping just two voting modes as per [1]: a) Majority approval, http://www.apache.org/foundation/glossary.html#MajorityApproval b) Lazy consensus, http://www.apache.org/foundation/glossary.html#LazyConsensus (and move to majority approval if there's a -1 there) With c) possible vetoes for commits as per [1] - those must have a clear technical justification to be considered valid. And where a) applies to almost everything, and b) saves time while allowing to move to a) if someone requests it with a -1. Removing the right to veto allows things to move forward, driven by the majority. It's no fun being in the minority, so in my experience over time people learn to adapt their proposals to make them acceptable, or make things more modular to cope with different views of the world. Again, you don't want to vote on each and every nitpick, but voting is a useful tool to avoid endless discussions on things that have various levels of importance for various people. -Bertrand [1] http://www.apache.org/foundation/voting.html
