Hi
On 4/9/24 21:32, Robert Landers wrote:
The Aviz RFC was put to a vote last year but didn't pass.
It would be really nice if votes weren't just a yes/no vote, but
yes/needs-more-work/no vote, where needs-more-work and no are
effectively the same in terms of passing the RFC, but needs-more-work
just means there is more to do (either addressing ugly syntax or the
idea is sound, but as it says, it needs more work), and can thus be
simply revoted on after concerns are addressed -- instead of creating
a whole new RFC that needs to pass the "not too similar to other RFCs
rule."
Re-proposing an RFC is allowed after 6 months even without substantial
changes:
https://github.com/php/policies/blob/main/feature-proposals.rst#resurrecting-rejected-proposals
Though I'd argue that property hooks passing would be a substantial
change of the broader context.
--------------
Relatedly, I would find an official "Abstain" option useful. Any
"Abstain" votes would be completely disregarded for the results, but it
would allow voters to indicate that they've read the RFC, thought about
it and don't sufficiently care either way to influence the results. As
an RFC author I think it would be useful information to me: Did some
folks not vote because they missed the RFC or because they are happy
with either result?
Best regards
Tim Düsterhus
