On Sun, 5 Apr 2020 at 13:05, Ilija Tovilo <tovilo.il...@gmail.com> wrote: > > "What are the rules here, can"
"... the rules are more what you'd call "guidelines" than actual rules." As a project we should clarify exactly what is meant to happen when issues are found in an RFC that affect how people are going to vote. But for this case; there is plenty of time until the deadline for RFCs that target PHP 8. As it's a small but non-trivial change, I'd recommend closing the vote, updating the RFC to either have the correct behaviour around precedence, or if it's not possible to do that, disallow code that has the ambiguous/surprising behaviour. Having what people are voting on change, when votes are currently being cast is a thing that leads to drama. Once that issue is fixed, then wait two weeks and put the RFC to a vote and it should sail through imo. > yours was literally the only criticism I received. In an attempt to set expectations; if a point is already being addressed as part of the discussion, it's unlikely that other people are going to "+1" that*. Extra email messages take up people's time and don't add much value. Currently it's the responsibility of the RFC author to make sure all points are addressed. Arguably that's something that could be split off to be a role done by someone else. cheers Dan Ack * moving to a discussion platform that did allow indicating agreement with an argument in a way that didn't take up people's time would be nice... -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
