Most votes are procedural. There are a couple specific veto votes:
1. You can veto a new committer or PMC member if you are on the PMC. 2. You can veto a specific code commit with a valid technical reason. This cannot be arbitrary or capricious - it has to be a specific technical reason and if that is addressed, things move on. This kind of veto has to be explicit, not just a standard “-1, im against this”. Larger issues - which java versions do we support, what back compat policies, git or svn - these are majority votes. Votes are a failure in a consensus community in general though. It’s best to have a discussion thread and a vote thread becomes a last resort when there is no way consensus will be reached. - Mark http://about.me/markrmiller > On Sep 15, 2014, at 2:45 PM, [email protected] wrote: > > Ryan, > I’m unclear on what makes a “procedural vote” as such. This seems to me to > be about code modifications — in a big way as it’s a large change to the > codebase. > > ~ David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
