rfc:abolish-narrow-margins

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
rfc:abolish-narrow-margins [2019/02/06 17:08]
nikic
rfc:abolish-narrow-margins [2019/02/08 08:49]
krakjoe
Line 3: Line 3:
   * Date: 2016-11-17   * Date: 2016-11-17
   * Author: krakjoe   * Author: krakjoe
-  * Status: Under Discussion+  * Status: Voting
   * First Published at: http://wiki.php.net/rfc/abolish-narrow-margins   * First Published at: http://wiki.php.net/rfc/abolish-narrow-margins
  
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 must require a super majority of 2/3.+This RFC proposes that **all** RFC's need to meet the same high standard: The main acceptance vote of any RFC must require a super majority of 2/3.
  
-This change means that the main vote in any RFC must have a super majority. +If this RFC is accepted, the original [[rfc:voting|voting RFC]] will be amended as per the Normative Text section of this RFC.
- +
-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 RFC ie. Their passing would result in merges into the source repository or changes to policy documentation that would otherwise not take place, regardless of the outcome of the main vote. +
- +
-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, and much more suited to a project the size and scope of PHP.+
  
 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 text ==== +==== Normative Text ====
- +
-If this RFC is accepted, the original [[rfc:voting|voting RFC]] will be amended as follows.+
  
 Under the "Required Majority" heading, the following text is **REMOVED**: Under the "Required Majority" heading, the following text is **REMOVED**:
Line 61: Line 48:
  
 A straight yes/no vote, 2/3 super majority required to pass. A straight yes/no vote, 2/3 super majority required to pass.
 +
 +<doodle title="Adopt the changes in this proposal?" auth="krakjoe" voteType="single" closed="false">
 +   * Yes
 +   * No
 +</doodle>
 +
 +Voting started on Friday 8th February, finishes Friday 22nd February.
  
 ===== Discussion Topics ====== ===== Discussion Topics ======
rfc/abolish-narrow-margins.txt · Last modified: 2019/02/22 11:45 by krakjoe