Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128205
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 24 Jul 2025 11:28:19 +0200
To: Andreas Heigl <andreas@heigl.org>
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] "Abstain" voting option for RFCs
In-Reply-To: <fc9c244b-38f5-4ced-9062-29d3609f73c9@heigl.org>
References: <b0d97beef95862524b329922522bbefe@bastelstu.be>
 <26c4161a-1520-4134-8fc1-74dc4a27c463@heigl.org>
 <CAMzRQTfVM=uOvA7-3CHV6AcO-Y-xPJV5QuSEueFO1iohMFdhKg@mail.gmail.com>
 <fc9c244b-38f5-4ced-9062-29d3609f73c9@heigl.org>
Message-ID: <a86ad6b0cf021170678f466e2f34e9a8@bastelstu.be>
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

Am 2025-07-23 17:34, schrieb Andreas Heigl:
> As you point out, the abstain alone solves a me "problem". Changing the 
> process just for that, seems overkill to me.

Requiring an "Abstain" option in the voting widget is a simple change to 
the process. It does not require any additional effort from RFC authors, 
since I'll make sure to add it to the voting widget in the RFC template 
(https://wiki.php.net/rfc/template) should this RFC pass.

I believe the proposal has sufficient merit on its own and also allows 
us to collect "hard data" that can be used as part of a discussion for 
future scope changes, such as an RFC quorum.

I don't believe having an "Abstain" option needs to be tied to larger 
changes to the process and I am not interested in increasing the scope 
of this RFC, intentionally leaving those to “Future Scope”. If you don't 
see the value right now, but don't outright reject the proposal due to 
being interested in future scope changes building on the proposal, 
abstaining from the vote would probably be the right decision :-)

Best regards
Tim Düsterhus