rfc:voting_who

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:voting_who [2011/11/09 08:03] – fix some links tyraelrfc:voting_who [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Request for Comments: How to write RFCs ======+====== Request for Comments: Who can vote? ======
   * Version: 0.1   * Version: 0.1
   * Date: 2011-11-09   * Date: 2011-11-09
   * Author: Ferenc Kovacs <tyra3l@gmail.com>   * Author: Ferenc Kovacs <tyra3l@gmail.com>
-  * Status: Draft+  * Status: Withdrawn
   * First Published at: https://wiki.php.net/rfc/voting_who   * First Published at: https://wiki.php.net/rfc/voting_who
  
Line 14: Line 14:
 ==== Voters ==== ==== Voters ====
  
-The original voting RFC allowed two distinct group to vote:+The original voting RFC allowed two distinct groups to vote:
   - People with php.net SVN accounts that have contributed code to PHP   - People with php.net SVN accounts that have contributed code to PHP
   - Representatives from the PHP community, that will be chosen by those with php.net SVN accounts   - Representatives from the PHP community, that will be chosen by those with php.net SVN accounts
  
-1, can be interpreted multiple ways, and it was misunderstood more than once, so the possible interpretations: 
-  - People having php-src karma, and at least one php-src commit. 
-  - People having svn accounts and at least one commit (this could mean documentation, test, pear/pecl, web related, etc.) 
  
-2, lacks the definition of how do we select those representatives.+Group 1, can be interpreted multiple ways, and it was misunderstood more than once, so the possible interpretations: 
 + 
 +  * People having php-src karma, and at least one php-src commit. 
 +  * People having svn accounts and at least one commit (this could mean documentation, test, pear/pecl, web related, etc.) 
 + 
 +Group 2, lacks the definition of how do we select those representatives.
  
 ===== Ideas ===== ===== Ideas =====
   * Maybe we could define different type of votes (language syntax change, adding new feature/extensions, etc.) and define the who can vote for each of those.   * Maybe we could define different type of votes (language syntax change, adding new feature/extensions, etc.) and define the who can vote for each of those.
     * This could be a good middle-ground between allowing qa/documentation/web people to vote on language level RFCs or not.     * This could be a good middle-ground between allowing qa/documentation/web people to vote on language level RFCs or not.
 +  * It is also a possibility to split the votes of the two groups "php devs" vs. "voice of the people".
 +    * This could also solve the issue that the two group have a different number of participants.
 +    * By that reasoning, RFCs could only be approved if the php developers and the community representatives are both supporting the RFC.
 +      * Of course that is also possible to only require the php-devs vote to pass for accepting an RFC, and the community votes would be used as a measure or guide, but that would somehow made the voting rights moot for the reps. 
   * We have to consider that:   * We have to consider that:
     * We have a large number of "sleeping" svn accounts     * We have a large number of "sleeping" svn accounts
Line 36: Line 42:
 ===== Changelog ===== ===== Changelog =====
 0.1 - Throwing some ideas around. 0.1 - Throwing some ideas around.
- 
  
rfc/voting_who.1320825781.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools