Re: [RFC][Vote] Throw Error in Extensions
| From: | Aaron Piotrowski | Date: | Thu, 30 Jun 2016 05:28:11 +0000 |
| Subject: | Re: [RFC][Vote] Throw Error in Extensions | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94331@lists.php.net to get a copy of this message | ||
Hi Dan,
> On Jun 29, 2016, at 3:41 PM, Dan Ackroyd <danack@basereality.com> wrote:
>
> For the record, I'm beginning to think the RFC process should probably
> be slightly more orchestrated, and RFCs should have a "pre-vote"
> announcement at least one week before the vote actually opens, when
> the RFC author thinks the discussion of the RFC is complete.
>
> This point would be the time for the implementations full impact on
> the PHP engine to be analyzed, and also when the final voting choice
> can be discussed/challenged before the voting is actually open.
>
Sorry if this RFC was a little rushed. I originally hoped to make these changes for 7, then the
original PR got pushed off to 7.1 and forgotten about until it was almost too late even for 7.1.
I agree that a pre-vote phase could be useful, as it may help bring more attention to an RFC before
voting actually opens. There seems to be a pattern of issues with RFCs not being discussed until
voting has begun. The pre-vote phase could replace one week of the discussion period, so an RFC
would still only need a minimum of two weeks between announcement and voting.
Cheers!
Aaron Piotrowski