Mark answers your question well. I agree with his assertion. I'll restate it for (hopefully added) clarity.
The goal is to avoid getting bogged down in votes and rule by committee. Ultimately, the one doing the work gets to make the decision. So, for release votes (and other majority consensus votes): No -1 is binding. Community members should indicate their support or otherwise of a -1 by casting (or changing) their vote as they see fit If there are no -1's the vote passes If there are more -1's than +1' the vote does not pass and the release is postponed If there are more +1's than -1's (and at least 3 +1's) the RM decides whether to proceed or not after having evaluated the justification for any -1's In all cases only PMC votes are binding, although it is good community practice to acknowledge all votes. So, for example, if there are 2 binding -1's, one non-binding -1 and 3 binding +1's an RM can choose to ignore or support the non-binding one as she feels is appropriate (if -1's are ignored a justification for doing so goes a long way). Ross Ross Gardler (@rgardler) Senior Technology Evangelist Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation On 19 February 2014 04:31, Ian Clelland <iclell...@chromium.org> wrote: > On Wed, Feb 19, 2014 at 4:26 AM, Ross Gardler <rgard...@opendirective.com > >wrote: > > > It's unfortunate that there are a couple of -1's on the current release > > VOTE thread at a time where the Cordova project is being asked to improve > > their release processes. So as to avoid a potentially bad experience > during > > this vote I want to ensure the community is aware of the voting > guidelines > > for releases, > > > > Specifically I want to remind the project that a release is not subject > to > > a veto. > > > Thanks for trying to clarify here, Ross. > > Does this mean that the vote thread here is absolutely binding? That is, if > there is no visible trail on the mailing list that anyone has changed their > minds, and after the allotted period, there are still more +1s than -1s > (from PMC members) that the release happens regardless? > > Ian > > > > A -1 is not a veto, it is merely an indication that the individual > > would prefer that the release be delayed to allow something to be fixed. > > > > For a release to be approved it requires majority approval (that is at > > least 3 +1's and more +1's than -1's) > > > > When a -1 is cast other community members should consider the severity of > > the issue identified and cast their vote accordingly. e.g. if someone > > identifies a serious security hole then it is expected that most people > > will cast their vote as -1 and the release will not happen. On the other > > hand harmless errors in documentation would not be supported by many -1's > > (the time is better spent fixing the documentation). > > > > In summary a -1 on a release vote is used to raise awareness of an issue > to > > ensure it is fixed either in this release (if important enough) or in a > > future release. > > > > Thanks, > > Ross > > > > > > > > > > Ross Gardler (@rgardler) > > Senior Technology Evangelist > > Microsoft Open Technologies, Inc. > > A subsidiary of Microsoft Corporation > > >
