Page History

{lozenge:title=Decision Making|width=100%|icon=!Decision Arrows 3 way 48x48.png!}
Within the Apache Flex project, different types of decisions require different forms of approval. This section defines how voting is performed, the types of approvals, and which types of decision require which type of approval.
{lozenge}

h2. {color:#2d5291}Voting{color}

Decisions regarding the project are made by votes on the primary project development mailing list (dev@flex.apache.org).

Where necessary, PMC voting may take place on the private Apache Flex PMC mailing list.

Votes are clearly indicated by subject line starting with \[VOTE\].

The vote email should indicate the voting approval type (Consensus, Lazy Consensus, Majority Approval or 2/3rds Majority Approval) and that should follow what is in these guidelines. If the voting approval type is not specified and is not covered by these guidelines it defaults to Consensus.

Voting is carried out by replying to the vote mail. Voting may take four flavors:
* \+1 "Yes," "Agree," or "the action should be performed." In general, this vote also indicates a willingness on the behalf of the voter in "making it happen".
* \+0 This vote indicates a willingness for the action under consideration to go ahead. The voter, however will not be able to help.
* \-0 This vote indicates that the voter does not, in general, agree with the proposed action but is not concerned enough to prevent the action going ahead.
* \-1 This is a negative vote. On issues where consensus is required, this vote counts as a veto. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a \-1 vote to include an alternative course of action.

You can also vote in fractions to indicate the strength of the vote, for example by voting \+0.5, \-0.5, \+0, \-0 etc etc. Only a full \-1 is considered a veto and releases and consensus require 3 full \+1 votes.

All participants, not just committers and PMC members, in the Flex project are encouraged to show their agreement with or against a particular action by voting.

For technical decisions (but not releases), the votes of committers are binding.

Non binding votes are still useful for those with binding votes to understand the perception of an action in the wider community.

For PMC decisions, only the votes of PMC members are binding.

Changes made to the Apache Flex codebase are made on a [Commit-then-review|http://www.apache.org/foundation/glossary.html#CommitThenReview] basis. Any change may be reverted by a veto (-1) in reply to the commit message sent when the commit is made.

\\

h4. {color:#2d5291}Voting timeframes{color}

Voting is open for 72 hours unless otherwise specified. When voting on release candidates the release manager at their discretion can carry over votes from the previous release candidate if there are minimal changes between release candidates. This should be indicated in the new release candidate vote.

If 72 hours pass and there's not enough votes for a resolution voting continues until cancelled or until there are enough votes for a resolution.

\\

h4. {color:#2d5291}Cancelling Votes{color}

A vote may be cancelled by the person who started the vote by sending an email with the subject line \[VOTE\]\[CANCEL\] to the mailing list.

\\

h4. {color:#2d5291}Vote Results{color}

Once a vote has been taken and the required timeframe has elapsed an email should be sent to the list with results of the vote and whether the vote passed or failed with a subject line of \[VOTE\]\[RESULT\].

\\

h4. {color:#2d5291}Changing Your Vote{color}

Anyone can change their vote until the required voting timeframe has passed and the results have been announced. Only a person's last vote counts in any total.
\\

h2. {color:#2d5291}Approvals{color}

These are the types of approvals that can be sought. Different actions require different types of approvals
* Consensus Approval - Consensus approval requires 3 binding \+1 votes and no binding vetoes.
* Lazy Consensus - Lazy consensus requires no \-1 binding votes ('silence gives assent').
* Majority Approval - A majority approval vote requires 3 binding \+1 votes and more binding \+1 votes than \-1 votes.
* 2/3rds Majority Approval - A 2/3rds majority approval vote requires at least 3 \+1 binding votes and twice as many \+1 binding votes as \-1 votes.

Majority Approval and 2/3 Majority Approval is based on the number of votes cast, not on the number of eligible voters.
\\

h2. {color:#2d5291}Vetoes{color}

A valid, binding veto cannot be overruled. A veto is only valid if it is accompanied by an explanation. The validity of a veto, if challenged, can be confirmed by anyone who has a binding vote. This does not necessarily signify agreement with the veto - merely that the veto is valid.

If you disagree with a valid veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, any action that has been vetoed must be reversed in a timely manner.

Majority votes can not be vetoed.