rfc:voting2017

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
rfc:voting2017 [2017/09/14 13:53]
zeev Be a bit more explicit regarding what happens post vote
rfc:voting2017 [2019/01/31 13:39] (current)
zeev
Line 1: Line 1:
-====== PHP RFC: RFC Workflow & Voting ====== +====== PHP RFC: RFC Workflow & Voting (2019 update) ====== 
-  * Version: 2.0.0001 +  * Version: 2.0.0002 
-  * Date: 2017+  * Date: 2019
   * Author: Zeev Suraski <zeev@php.net>   * Author: Zeev Suraski <zeev@php.net>
-  * Status: Draft (or Under Discussion or Accepted or Declined)+  * Status: Under Discussion
   * First Published at: http://wiki.php.net/rfc/voting2017   * First Published at: http://wiki.php.net/rfc/voting2017
  
Line 36: Line 36:
   * **RFC**: Request For Comments for a proposed Change to PHP or for a PHP Packaging Decision, published on http://wiki.php.net/rfc/.   * **RFC**: Request For Comments for a proposed Change to PHP or for a PHP Packaging Decision, published on http://wiki.php.net/rfc/.
  
-  * **Implementation Decisions:**  Decision regarding the technical implementation of PHP or any of its bundled extension, that do not have any impact on end users (with the exception of performance improvement). +  * **Implementation Decisions:**  Decisions regarding the technical implementation of PHP or any of its bundled extension, that do not have any impact on end users (with the exception of performance improvement).  Explicitly, these **do not include** added, altered, removed or deprecated functionality.
- +
-  * **Release Manager(s)**+
  
   * **PHP**:  The PHP package in source code or binary form, that are available on the main downloads page at http://www.php.net   * **PHP**:  The PHP package in source code or binary form, that are available on the main downloads page at http://www.php.net
Line 52: Line 50:
 **PHP Packaging Decisions** must also be discussed ahead of time on Internals, and must go through a vote.  However, unlike Changes to PHP, these decisions are a matter of preference - preference that can be changed with little or no consequences for future versions.  Given their shorter term impact and relative low reversal costs, a simple majority is sufficient (>50.0%, or in the case of multiple choice - the options that wins the most votes).  **PHP Packaging Decisions** must also be discussed ahead of time on Internals, and must go through a vote.  However, unlike Changes to PHP, these decisions are a matter of preference - preference that can be changed with little or no consequences for future versions.  Given their shorter term impact and relative low reversal costs, a simple majority is sufficient (>50.0%, or in the case of multiple choice - the options that wins the most votes). 
  
-**Implementation Decisions** generally do not require voting, but with the exception of small, tactical decisions (such as fixing a bug with just a few lines of code) - developers are still encouraged to bring it up for discussion on Internals.  As far as Implementation Decisions are concerned, the active maintainers of the particular piece of code (as reflected via source control) will have the jurisdiction.  Please note that Implementation Decisions explicitly do not include such decisions that have an impact on end user functionality, or that degrade performance in a noticeable way.  Such decisions are considered Changes to PHP, and must follow the rules above.+**Implementation Decisions** as defined above do not require voting, as they don't have an impact on end users.  However, developers are still encouraged to bring implementation decisions up for discussion on Internals, especially ones dealing with more fundamental parts of PHP, or ones which involve substantial refactoring.  As far as Implementation Decisions are concerned, the active maintainers of the particular piece of code (as reflected via source control) are the ones who have the jurisdiction to take them. 
 + 
 +Please note that Implementation Decisions explicitly do not include such decisions that have an impact on end user functionality, or that degrade performance in a noticeable way.  Such decisions are considered Changes to PHP, and must follow the rules above.
  
 ==== RFC Workflow ==== ==== RFC Workflow ====
rfc/voting2017.1505397199.txt.gz · Last modified: 2017/09/22 13:28 (external edit)