voting
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Last revision | |||
— | voting [2019/02/09 23:19] – created stas | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Introduction ===== | ||
+ | This document describes the procedure to propose an idea for adoption by the PHP community and decide if the community accepts or rejects the idea. | ||
+ | |||
+ | ===== Proposal initiation ===== | ||
+ | |||
+ | Proposal is formally initiated by creating an RFC on PHP wiki and announcing it on the list. If the proposal is a repeated discussion of an existing RFC, with or without modification, | ||
+ | |||
+ | The announcement will be done in a way that's easy to flag & follow, e.g. - by **[RFC]** in the subject line followed by the title of the RFC. | ||
+ | |||
+ | The proposal should be initiated by one of its authors. If the proposal is a repeated one, re-proposed by somebody else, the proposer should discuss it with the original author, if possible, and add himself to the RFC author list before proposing it. | ||
+ | |||
+ | If the proposer is not a member of php.net and thus can not create RFCs on the wiki, they should recruit one of the members for help or request membership. | ||
+ | |||
+ | ===== Discussion period ===== | ||
+ | |||
+ | There' | ||
+ | |||
+ | This does not preclude discussion on the merits on any idea or proposal on the list without formally submitting it as a proposal, but the discussion time is measured only since the formal discussion announcement as described above. | ||
+ | |||
+ | ===== Voting ===== | ||
+ | |||
+ | The author decides when it's time to move ahead and call a vote on the RFC. If the author feels that there' | ||
+ | |||
+ | The vote is announced on the mailing list in a separate thread by sending an email with the subject **[VOTE]**. It should reference the RFCs being voted on and if there are different options discussed, explain these options. It should also contain the URL of the page where the vote is taking place. | ||
+ | |||
+ | The voting has minimal period of 1 week, which can be extended when circumstances warrant it. | ||
+ | |||
+ | ===== Required Majority ===== | ||
+ | |||
+ | Given that changes to languages (as opposed to changes to apps or even frameworks) are for the most part irreversible - the purpose of the vote is to ensure that there' | ||
+ | |||
+ | |||
+ | ===== Resurrecting Rejected Proposals ===== | ||
+ | |||
+ | In order to save valuable time, it will not be allowed to bring up a rejected proposal up for another vote, unless one of the following happens: | ||
+ | * 6 months pass from the time of the previous vote, OR | ||
+ | * The author(s) make substantial changes to the proposal. | ||
+ | |||
+ | |||
+ | ===== Who can vote ===== | ||
+ | |||
+ | There' | ||
+ | |||
+ | The proposal here is for two audiences to participate in the voting process: | ||
+ | * People with php.net VCS accounts that have contributed code to PHP | ||
+ | * Representatives from the PHP community, that will be chosen by those with php.net VCS accounts | ||
+ | * Lead developers of PHP based projects (frameworks, | ||
+ | * regular participant of internals discussions | ||
+ | |||
+ | ===== RFC Proposer ===== | ||
+ | |||
+ | * Proposers vote with +1 on their own RFC per default if they are allowed to vote |
voting.txt · Last modified: 2019/09/16 08:41 by krakjoe