> Am 03.02.2019 um 06:18 schrieb Zeev Suraski <vsura...@gmail.com>: > >> -----Original Message----- >> From: Nikita Popov <nikita....@gmail.com> >> Sent: Saturday, February 2, 2019 6:24 PM >> To: PHP internals <internals@lists.php.net> >> Subject: [PHP-DEV] Alternative voting reform: Streamlining the RFC process >> >> Hi internals, >> >> After discussing the topic with a number of current and former contributors, >> I >> feel that the workflow & voting RFC currently under discussion is moving us >> in >> the wrong direction. I will not comment on the rather questionable proposed >> changes to voting eligibility, as these are already extensively discussed in >> the >> RFC thread. > > Personally, I find any proposal that does not deal with clearly defining > voting eligibility not only questionable, but a non-starter, that has no > parallels in any other major Open Source projects. > > The suggestion that the new RFC makes life more difficult, compared to the > current Voting RFC, is simply wrong. It is, in fact, very much the same - > except it's a lot more well defined in terms of 'what happens if' - which in > the years since the 2011 Voting RFC was enacted became a de-facto wild-west. > > It may initially feel warm & fuzzy to have vague, fluid rules that are > remarkably open to interpretation. But it's not a good idea at all. > > Zeev
Hey Zeev, why is dealing with voting eligibility a requirement for a new RFC dealing with the RFC process? Everything which is not dealt with, is simply inherited from status quo. And I personally don't think the current rules regarding voting eligibility, while possibly not perfect, are in such a bad state that they immediately need a rework. The door to concrete, separate proposals fixing voting eligibility is not closed with this RFC. You are always free to open a new specific RFC and discuss about a voting eligibility proposal. In addition, the newly proposed RFC here is absolutely not vague. It is pretty well defined, showing a few clear boundaries. For everything else it is the task of the voter to establish whether a RFC is ready and shall be voted in as is. It's precisely that which makes a great voting process. In particular with a 2/3 required majority, I strongly doubt that bullshit RFCs which are quickly proposed and moved to vote, will ever be accepted. I trust our voters enough to know when something should definitely not be accepted. And I strongly hope that you are not lacking faith in us PHP RFC voters, that you feel like you couldn't trust us to apply sensible judgement to each RFC. Thanks, Bob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
