On Tue, 30 Jul 2019 at 20:09, Zeev Suraski <z...@php.net> wrote: > > If you propose, be ready to discuss it in good faith, including > with folks with opposing views who take their time to write detailed feedback.
Some of the points raised during discussions are not technical arguments that can be addressed, some of them are concerns about what the development experience will be like. They are valid concerns but it's impossible to give a definitive 100% non-criticisable response to them. It's not always possibly to convince everyone that an idea is going to be a good idea. This is why we have voting rather than consensus, so that after people have said the things they want to say, we can have a vote and move forward, rather than getting stuck and both sides trying to 'win' an argument where people can have valid differences of opinion. > There's a reason we call RFCs RFCs. Yes, so people can make comments on them, not that people have to win over every voter. > And it absolutely means defending their proposal, including from > folks who may have issues with them. > > If they do - it's absolutely their responsibility > to defend their proposal Zeev, this isn't a rule that has been agreed. If you wish to change the rules, to include the idea of having a "long-term view" special committee or similar, please do propose that as an RFC to be discussed. Or if you want some way of formally listing "unaddressed concerns" in the RFC, that could also be discussed. But making vague threats to try to influence other contributors is completely inappropriate behaviour. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
