rfc:voting_who
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| rfc:voting_who [2011/11/09 09:10] – [Voters] formatting salathe | rfc:voting_who [2012/04/16 08:00] – withdrawn tyrael | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Request for Comments: | + | ====== Request for Comments: |
| * Version: 0.1 | * Version: 0.1 | ||
| * Date: 2011-11-09 | * Date: 2011-11-09 | ||
| * Author: Ferenc Kovacs < | * Author: Ferenc Kovacs < | ||
| - | * Status: | + | * Status: |
| * First Published at: https:// | * First Published at: https:// | ||
| Line 29: | Line 29: | ||
| * Maybe we could define different type of votes (language syntax change, adding new feature/ | * Maybe we could define different type of votes (language syntax change, adding new feature/ | ||
| * This could be a good middle-ground between allowing qa/ | * This could be a good middle-ground between allowing qa/ | ||
| + | * 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 " | * We have a large number of " | ||
| Line 38: | Line 42: | ||
| ===== Changelog ===== | ===== Changelog ===== | ||
| 0.1 - Throwing some ideas around. | 0.1 - Throwing some ideas around. | ||
| - | |||
rfc/voting_who.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1