rfc:change_required_votes_to_two_thirds
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
rfc:change_required_votes_to_two_thirds [2014/11/19 19:27] – levim | rfc:change_required_votes_to_two_thirds [2014/11/19 19:29] – levim | ||
---|---|---|---|
Line 11: | Line 11: | ||
Motivations for requiring 2/3 of the votes or more for an RFC to pass: | Motivations for requiring 2/3 of the votes or more for an RFC to pass: | ||
- | * Almost every time someone proposes an RFC and claims 1/2 + 1 there is a discussion about whether or not the RFC *really* | + | * Almost every time someone proposes an RFC and claims 1/2 + 1 there is a discussion about whether or not the RFC is allowed to get away with 1/2 + 1 instead of 2/3. Making all RFCs require the same percentage will cut down on noise on the list. |
* Requiring 2/3 for all RFCs means that RFC authors need to work harder to make the RFCs appeal to more people; this theoretically would mean that more effort goes into the RFC and the end result for all users is better. | * Requiring 2/3 for all RFCs means that RFC authors need to work harder to make the RFCs appeal to more people; this theoretically would mean that more effort goes into the RFC and the end result for all users is better. | ||
* Making changes are harder to undo than they are to do. This means that any feature we add or change will be there for a long time. If we can't get 2/3 of voters to agree that something is done right then it should not go into PHP core. | * Making changes are harder to undo than they are to do. This means that any feature we add or change will be there for a long time. If we can't get 2/3 of voters to agree that something is done right then it should not go into PHP core. |
rfc/change_required_votes_to_two_thirds.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1