rfc:abolish-narrow-margins
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:abolish-narrow-margins [2019/02/06 17:06] – nikic | rfc:abolish-narrow-margins [2019/02/07 17:23] – nikic | ||
---|---|---|---|
Line 16: | Line 16: | ||
RFC's come in the following two categories: | RFC's come in the following two categories: | ||
+ | * Proposals to make changes to PHP | ||
* Proposals to amend or create policy documents | * Proposals to amend or create policy documents | ||
- | * Proposals to merge code into php-src | ||
- | This RFC proposes that //all// RFC's need to meet the same high standard.: Any vote that would result in merges into the source repository, or amend or create policy documentation | + | This RFC proposes that **all** RFC's need to meet the same high standard: |
- | This change means that the main vote in any RFC must have a super majority. | + | If this RFC is accepted, |
- | + | ||
- | Subsidiary votes come in the following two categories: | + | |
- | + | ||
- | - Vote to resolve implementation details - ie. Choose between version X and version Y of an implementation for a main vote. | + | |
- | - Vote that could have been run as a separate | + | |
- | + | ||
- | A subsidiary vote of type 1 may require a slim majority (as per the current definition). | + | |
- | + | ||
- | A subsidiary vote of type 2 must require a super majority (as per the current definition). | + | |
- | + | ||
- | These new rules are unambiguous, | + | |
These rules shall apply to any RFC whose vote ends after this RFC is accepted, should this RFC be accepted. | These rules shall apply to any RFC whose vote ends after this RFC is accepted, should this RFC be accepted. | ||
- | ==== Normative | + | ==== Normative |
- | + | ||
- | If this RFC is accepted, the original [[rfc: | + | |
Under the " | Under the " | ||
Line 51: | Line 38: | ||
The primary vote of an RFC, determining overall acceptance of the proposal, may only have two voting options and requires a 2/3 majority. This means that the number of Yes votes must be greater than or equal to the number of No votes multiplied by two. | The primary vote of an RFC, determining overall acceptance of the proposal, may only have two voting options and requires a 2/3 majority. This means that the number of Yes votes must be greater than or equal to the number of No votes multiplied by two. | ||
- | Additionally, | + | Additionally, |
For procedural reasons, multiple RFCs may be combined into one, in which case there may be multiple primary votes. Combining multiple RFCs into one does not allow turning a primary vote into a secondary vote. | For procedural reasons, multiple RFCs may be combined into one, in which case there may be multiple primary votes. Combining multiple RFCs into one does not allow turning a primary vote into a secondary vote. |
rfc/abolish-narrow-margins.txt · Last modified: 2019/02/22 11:45 by krakjoe