Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128734
Message-ID: <44951bf1-75f3-4cdd-ac29-5fa82ec91482@bastelstu.be>
Date: Fri, 26 Sep 2025 17:20:34 +0200
Precedence: list
MIME-Version: 1.0
Subject: Re: [PHP-DEV] [RFC] Clarify discussion and voting period rules
To: Larry Garfield <larry@garfieldtech.com>,
 php internals <internals@lists.php.net>
References: <53cdbf5b-7c6e-4ba1-9987-332634cab527@bastelstu.be>
 <29c9d6cfcc2928d3805596416edbff6e@bastelstu.be>
 <92a59844e30a9ca0550456886913fdb1@bastelstu.be>
 <1a9046bf-2dcc-4049-b1e7-e82d4230b0f6@app.fastmail.com>
 <AE3E5C12-2599-4361-9CD0-24ACF2AE175B@nicksdot.dev>
 <fafb5a7e-efe2-4024-b5c9-74e60805f06f@app.fastmail.com>
Content-Language: en-US
In-Reply-To: <fafb5a7e-efe2-4024-b5c9-74e60805f06f@app.fastmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=)

Hi

On 9/25/25 16:46, Larry Garfield wrote:
> I'm inclined to agree.  If within 48 hours it's obvious that an RFC is doomed, I don't see an issue with the author going "eh, never mind" and saving everyone 2 weeks of waiting.  If there's some key controversial bit they can change and try again, I think that's reasonable.  Probably needs a Major Change cooldown period, but that's fine.

The current proposal already specifies that canceling a vote is a “Major 
change”. I also expect that any changes made *after* canceling and 
*before* restarting the vote would be Major changes themselves, so 
unless the changes happen right away and are then uncontentious, I would 
expect the new vote to come no earlier than 3-4 weeks after the cancelation.

Best regards
Tim Düsterhus