On Thu, Jan 31, 2019, 7:58 AM Kalle Sommer Nielsen <ka...@php.net wrote:
> Hi Zeev > > Den tor. 31. jan. 2019 kl. 15.44 skrev Zeev Suraski <z...@php.net>: > > > > Without further ado, an RFC that’s attempting to comprehensively solve > many of the issues that have plagued our RFC process since it was hastily > introduced in 2011: > > > > > > > > https://wiki.php.net/rfc/voting2019 > > I wholeheartedly disagree with the PHP-FIG special exception to who > can vote, call me biased but I do not believe it serves any purpose > and is absurd. People who actively work on PHP, should be the ones to > be able to have a choice, I think that should be reserved for any > contributor who puts effort working on PHP. > > I do understand that we are the language and our work affects the > others the most. However making special exceptions for who can vote > and essentially having a say from an external source in what I in > theory need to help maintain as a PHP Core Developer is terrible. Why > not allow WordPress Core Developers to have a say instead, as their > work has a larger impact on the usage of PHP? (That was obviously a > bit of sarcasm, the last part). We are not allowed to vote at their > individual projects features (nor do we need to have a say if we are > not actively involved in the development of said projects or > organizations) and I stand very strongly behind that belief. > > Besides this, it also creates uncertainty about who elects such, and > simply should be dropped from the voting RFC as it was already fairly > unclear from the original one. > > The contributors appendix also lists ChangeLog, SVN Migration etc, > something to keep in mind if this RFC is moved forward to filter the > list. > > > Do I understand the PHP Packaging Decisions right that it requires to > vote for a timeline for each version? I remember we have different > opinions raised regarding the time to a new major version (should we > have 7.4 vs go to 8.0, same for the 5 to 7 transition back then > regarding a 5.7). This is the only issue I can think of and should be > changed to requiring a vote if there is a dispute in regards to what > the next version should be. As I don't really wanna vote just to vote > for each of the minor versions of 8 once a year when its the most > logical reason to go to 8.1 from 8.0, and so on until we reach the > point where the next major is considerable. > > > I think changes like the requiring a patch for RFCs is a very welcomed > addition. > > -- > regards, > > Kalle Sommer Nielsen > ka...@php.net > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php Given how complex and controversial this question of restricting who can vote is, I propose that it be moved to its own RFC instead of being bundled with this one. It would certainly boost likelihood of passage, if nothing else, as there are a lot of good ideas in this RFC. --Kris > >
