Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128185 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id 9808D1A00BC for ; Tue, 22 Jul 2025 22:03:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1753221699; bh=wQsUF0DcyCTAKMSMHReCQPMGMuQ2xBXsgZyheic35do=; h=Date:From:To:Subject:From; b=lcqAV9gUK1ZjKu+R1anHXDNS8+AOACkw4nkJMaN7JAHF5PWakr1TdAzr2EEiu708H yVet4SLS8yGUFE/5geuDADaAJvAo724GF7HBgSUOmHa9ea6KElkpdfwd5Pw1k34sDi gk/K7hhooGnPa48yjuVwDOzh0xfxA5uFuB/JcMf1jWjTHRYrx8QLR2QSOIHLRy2yUI 09DC+yFBY8mTMOgMbcdjen8eDvqFJPmhvMucBZ5a6z213O1VI3OPQ8uSzIUCWJCMrz cmBnofdGa+g3XaZmJfytJCxEwMAuSs6/T5bCvb0Rvo4sdrVab+6ngPw/ccMX7ZtjAP fOpMw4mkq7GpA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 30B05180061 for ; Tue, 22 Jul 2025 22:01:38 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 22 Jul 2025 22:01:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1753221801; bh=xRvJMEfAPoxJMDowudNmGlzW/IbfZ8BTa42PAeZBlew=; h=MIME-Version:Date:From:To:Subject:Message-ID:Content-Type:from:to: cc:subject:message-id; b=i6/WZ4JzYsu47HGuHxYIcfa0XEL7lxuRf2qcbyMIOeKTyNoZ6APFMcjR3dkV3MnBW fSg81oACv1Bi+M1YH5CxMMSjOryD8LTf2ZivkgMn4KvQGzkpz8AMHrxyRFLfUpVxrG vg7FNp5iGrMONOZEkS3WrNU1AfS/QQpMPnP8bFYOOYhu1sMKdojj9wYC9aMExgzrai BtoMPcUpIc7Vv2sWHfFMhS0aoG7EfPK91L5Ce1GT56o8wEy4AYPz9dCDLGiXMJpT/9 4dHdiRYHoJHUaBe+nQOmH1+IiUb8M0X9JLwi1UDRfOfXYAT7AteH7qivYHtfRPr1cC kFvTkN1L+YwLg== Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Date: Wed, 23 Jul 2025 00:03:20 +0200 To: php internals Subject: [PHP-DEV] [RFC] "Abstain" voting option for RFCs Message-ID: 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 Adding an "Abstain" option to RFCs was an idea that floated around multiple times in the past and it now came up again as part of (more than) one of the RFCs that recently went to vote. I've therefore finally written up a policy RFC to add such an option. As part of doing that I have also cleaned up the phrasing of the corresponding section and added some clarification of what I believe matches the current policy and just wasn't written down, particularly around "secondary votes". Please find the RFC at: https://wiki.php.net/rfc/rfc_vote_abstain And the PR at: https://github.com/php/policies/pull/20 As with all policy RFCs, the corresponding PR to the policies repository will be the authoritative source of the proposal and the RFC (and discussion) will only provide extra context. Please do not comment on the PR (except for minor typographical or phrasing clarification suggestions). For comments regarding the actual "policy" reply to this discussion thread for proper visibility instead and I'll make sure to incorporate them as appropriate. This message is intended to begin the official discussion period. While it would be great to bring this policy into effect before any RFCs targeting PHP 8.6, I'll make sure to monitor the (list) activity with regard to folks being busy finalizing their own RFCs (and enjoying their summer vacations [1]) to make sure everyone had plenty of opportunity to participate in the discussion, so I would expect a vote around end of August at the earliest. Best regards Tim Düsterhus [1] I'll be on vacation myself in August :-)