On Fri, Mar 20, 2015 at 1:21 PM, François Laupretre <franc...@php.net> wrote: > May I also add that it is not the first time people raise concerns about RFCs > when vote starts. On different occasions, it was clear that most had not read > the RFC before the vote was announced. I even have two RFCs which were > planned for 7.0 and won't be in because I had to stop the vote and restart a > discussion. When we have short timelines, as for 7.0, it's a real problem > because restarting a discussion easily adds one month to the approval > process. Actually, I don't know if, in this case, I shouldn't reply that the > discussion is over and that it's just too late to wake up.
The problem is not the RFC process but us accepting idealistic timelnes. It is why I did not vote (for the ones that did not respect the RFC process) or no for the ones I totally disagree with. But this is off topic imho, we took these decisions now we have to work with that. In any case, one thing has to end, the playing with the rules. Discussions must happen for at least two weeks before a RFC goes to vote, mail must be sent to announce each phase. And last but not least, editing a RFC during or after the votes in a way that it changes what people votes for or against is not something I want to see. We have to solve this issue. Learning by doing :) Cheers, -- Pierre @pierrejoye | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
