It is commonly the case that RFC voters do not feel strongly about an individual RFC, but the current voting guidelines make it impossible to express this.
The current voting guidelines for RFCs require a binary vote with a 2/3 majority to accept RFCs. It is often the case that RFC voters do not feel strongly about an individual RFC, despite participating in the discussion. When it goes to vote, they are unable to express their opinion on the RFC itself, leaving some ambiguity whether they “missed the vote” or whether they just don't feel strongly about it, particularly when it's a multi-vote RFC. They might also feel compelled to cast a vote just as a “sign of activity”, or to prevent people from reaching out to them, inquiring about if they missed the RFC.
The topic of an explicit “Abstain” option has therefore come up multiple times during informal discussions and this RFC intends to formalize it. With regard to the results of a vote, the “Abstain” option behaves identically to not casting a vote.
Accept the policy in https://github.com/php/policies/pull/20.
Besides adding the requirement of an “Abstain” option to the primary vote of an RFC it also updates the language of the “voting methodology” section to be clearer, particularly with regard to secondary votes.
None.
Despite technically being in violation of the current voting guidelines, this RFC includes the “Abstain” option in the primary vote to “dog-food” the proposal (the “Abstain” option could legally be included as a secondary vote without an effect).
After the RFC is implemented, this section should contain:
None.
None.