Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128770 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 7ED271A00BC for ; Fri, 3 Oct 2025 14:10:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1759500573; bh=L4nQ5d8nzkdusWguB6dOkVqaCnZHBX3p2n3Ea9uwtiU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=IExO17PU6CO18XzC/GHOouG/FKbmZQr7al6qgwqRBLBNjK4nResp2ZBSR2oCVvLo1 5wkLAa6HjgxCTBw/SNNhn90ZDe6Mjblpg66fCsygbuvZ4ATaDGmEIXDfh3uXqn6UWR nRw05rr1RsJoPAApconAGX+NtLvZs9GkK/5okArvJWfOlv3W9+s4QsdD0TSQaoL2SF t65X4bAS4H0CcJ87WQVtXPsikVizMFHSVAiuTbnGsCQphhj+diVkVJKLCopL1zgYpb nhamEuH07cnrR3fXa/OFOfqsBsgPHij5w8C4msGyWHrQ4hsaEyqSG/e9UAy1XPJXt/ ZymIoFSGSKMtw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 50BA5180032 for ; Fri, 3 Oct 2025 14:09:33 +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.2 required=5.0 tests=BAYES_40,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: No 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 ; Fri, 3 Oct 2025 14:09:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1759500649; bh=qPGR6gC3NzDNabJj0F0yOJx4Sgac9tVXY427nCRsfog=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=DsPptScIO82K3pn0JvlL8euBUkAc162ScNTQqJFAd5AJOpAJqULacaB0s6Qy+qKIw ToyjhRoJmi1tG2vX6bzTPzWbw9Tlsz6R0stqccCkp9ayea303xBmAMEPSMIF12zyRK kQTen9DnJIEvsrybLyLE0eWUde+9n5XzPDbFkh8ndb7TzYLXWsuj3/lN+Q/xKC3J5P 7PR7iYwAqxiOrxfuxAyqSVsDrg+ox5rOpqJTG9sw1V5y6pRRHMvj/YwcCK7lhI2LWd DBconYO8lanllxvKKckd7pdm5IdICR53XlQnDnqV9f1QhwXDRMAdWoWCnr5LW8tLGo 3qHPnNDPdk1tQ== Precedence: list list-help: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Fri, 03 Oct 2025 16:10:49 +0200 To: youkidearitai Cc: php internals Subject: Re: [PHP-DEV] [RFC] Clarify discussion and voting period rules In-Reply-To: References: <53cdbf5b-7c6e-4ba1-9987-332634cab527@bastelstu.be> <29c9d6cfcc2928d3805596416edbff6e@bastelstu.be> <92a59844e30a9ca0550456886913fdb1@bastelstu.be> <1a9046bf-2dcc-4049-b1e7-e82d4230b0f6@app.fastmail.com> <7f1bce1f-f80b-48e7-962a-539172a85a6d@bastelstu.be> 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 Am 2025-09-29 14:13, schrieb youkidearitai: > Anyway, I thought about this topic few days. > As long as there are people who don't take part in the discussion in > "Under Discussion" phase, I'll say no to this topic. > > I was concerned that "Clarify " would put people who are not native > English at a disadvantage (I'm writing use Google translate too). > This will not clear the concerns. > (However, I don't have grant for vote an RFC) > > First, we must join to discussion in "Under Discussion" phase. As mentioned in my previous email, I believe there is a misunderstanding. My RFC is not intended to make it harder to make RFCs or to put folks who are not native speakers of English at a disadvantage (I am not a native speaker myself). It is formalizing some rules around the length of the discussion period to ensure there is sufficient time for folks to provide feedback after every change made. Looking at your RFC specifically, you would have needed to do the following things differently: - You made minor clarification changes on 2025-06-27. You would have needed to mention them on the list and wait for 7 days before starting the initial vote. - Similarly for the revision, you removed the `$strength` parameter on 2025-07-15. This was a major change which you announced on the list, but you would have needed to wait 14 days before starting the vote, you only waited 10 days. - And on 2025-07-22 there was some clarification, which was not announced on the list. - You would have needed to add a link to the mailing list discussion to the RFC itself. Everything else was already compliant from what I see. I think you can see how “announcing changes and waiting a little” is not significantly changing or complicating the RFC process. Best regards Tim Düsterhus