On 19/03/2017 19:32, Jakub Zelenka wrote:
I completely disagree with this. If there is not enough votes, it means that poeple either don't care (possibly don't have time or don't read properly mailing list) or don't understand the proposed thing.
Yes, those are the most likely reasons. There is also the possibility that for some technical or timing reason people missed the announcement.
I think it shousld up to the maintainer to decide in such case and not to block a feature because not enaugh people is interested in it.
There is currently nobody authorised to make that decision, and granting it to extension maintainers feels like a significant change to that role. As I understand it, one of the big differences between a PECL extension and a bundled one is that once in core, it's subject to decision-making by the whole project, not the authors of the code.
But even if we leave it as it is (accept it with only few votes) it is still much better than block it if there is no interest.
The entire RFC and voting process assumes that "no change" is the default option - a language change requires two-thirds to make the change, not two-thirds to reject it. If there were a "quorum" rule, it would be entirely consistent for not enough votes to have the same effect as an insufficiently large majority, and reject the change.
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
