Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128599 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 9B6EE1A00BC for ; Mon, 1 Sep 2025 11:09:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1756724878; bh=c3TNkmh5uaEDZj+P7uh2qde30JY15FNb/UAmNfhrtR0=; h=Date:Subject:To:References:From:In-Reply-To:From; b=Ggxe9D1lDwXvK3pR7lS3BZ5pM4sSPhujGiWv6QmiFgTAi7b9el/zDWha46PHnQ0R1 ubeYvau4esIdUDquuGjvKJK3QnWBGkrVoCg6U5LL/ZT0bMYopdQeTIwks4pulA3fuw +uVr/MwydWv8HSKvYPu08dvUH0aQ5HruEoHvfCpn7Cqr+5tufBrGYnrDC5ph/96HHL 2L2a1HJQPCISaigOx4JOokqSm36XqXVf+9kLb5px02wC4sboXPvu3FCB8JC5iJjiXw ZqkB+2GinqdIxHspG9GsrCMDp+83KnNMlaz6qgDfx7d701LxBeYs6huYCfpJU5p0PE fU670m1KvmCcw== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A5DB6180054 for ; Mon, 1 Sep 2025 11:07:57 +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=-1.4 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_MISSING,HTML_MESSAGE, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from fhigh-a7-smtp.messagingengine.com (fhigh-a7-smtp.messagingengine.com [103.168.172.158]) (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 ; Mon, 1 Sep 2025 11:07:57 +0000 (UTC) Received: from phl-compute-06.internal (phl-compute-06.internal [10.202.2.46]) by mailfhigh.phl.internal (Postfix) with ESMTP id CA09C14000FC; Mon, 1 Sep 2025 07:09:26 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-06.internal (MEProxy); Mon, 01 Sep 2025 07:09:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=allenjb.me.uk; h=cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1756724966; x=1756811366; bh=SSp63fJo4X koS9Jae1V7d1W01kdUmxmFUGF5ubMnn1w=; b=jdVZGxp434GvWbR9YPPW1Ypxs2 X+7DpJFzOXZCdDbaq/RvxLSFTBQ2QHVP9xCjhg5THQom5WrFxgyUS7g1CEysXggu 9DlH7p96Yg3vzs7CTIpy2LCVpxWejGsMciPEZX9fK1u7FIPBaIcOSJXK25zhdp9N zBwvyHA/IYc1D9JCsAO8VRULA2+3Mif9YHuZdNlKYB7pe204W2SRHCpL3gfA83oi ZlxJMeEgVhFwSRnBx/rq7H+R+FfokE8hq56bP8tp+d1GWVy/pJnYax0QN4zqH5oW 5k6tXP9qAKjTx40+72aB8TTdB+VTWnB8/YO9aWmMvwSpHtjLeF2cG/bjIVTQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1756724966; x=1756811366; bh=SSp63fJo4XkoS9Jae1V7d1W01kdUmxmFUGF 5ubMnn1w=; b=cn22McGfh498WBT7ePMiHOsnwEoqddKdVMziFj47Vj4eEdPjNmL fU8t6FC90thpH/Z1HUiRaWvnr6DRn8fDLcOIle4H0y7s0aAvudDKKSdz6wNGlP7p a9pYh1luqCNNHwfMz0W7p4EIJenPH2Qs+lJ9FUazkF9uM67S08s0MFqgziQ6vihx ghBbf5LKmD5nLLQf2kpgxm28mlGx+ZvxaDvNTqMPcDmVCRze57kIHf773lhlmJ4O ToKh0IR9gSGdbrOQM+mmpd3rzqftqeFSRfFH/gOlbS1uSZjI40lbHDNNH3Z7Y9P/ z9c2JVehEAMU3av/D+nZfXXKKyhKIDXtCQg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdduledvtddtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfuffvfhfhjgesrgdtreertd dvjeenucfhrhhomheptehllhgvnhfluecuoehphhhprdhlihhsthhssegrlhhlvghnjhgs rdhmvgdruhhkqeenucggtffrrghtthgvrhhnpeejveffkeetjeevheefhedtkeekledvje evtedvtefhudeuvefhueeikeegheehkeenucffohhmrghinhepvgigthgvrhhnrghlshdr ihhonecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepph hhphdrlhhishhtshesrghllhgvnhhjsgdrmhgvrdhukhdpnhgspghrtghpthhtohepvddp mhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepphhhphesnhhitghkshguohhtrdguvg hvpdhrtghpthhtohepihhnthgvrhhnrghlsheslhhishhtshdrphhhphdrnhgvth X-ME-Proxy: Feedback-ID: idf69468d:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 1 Sep 2025 07:09:25 -0400 (EDT) Content-Type: multipart/alternative; boundary="------------zL3oZLfbuVo7VDjBj4MqYFXa" Message-ID: <560f1bd3-5cf5-435c-ac15-65f84af122ac@allenjb.me.uk> Date: Mon, 1 Sep 2025 12:09:24 +0100 Precedence: list list-help: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PHP-DEV] Reference of discussion in RFCs To: Nick , internals@lists.php.net References: <30FD734F-2ED4-4D48-823A-3E4E0F265D38@nicksdot.dev> Content-Language: en-US In-Reply-To: <30FD734F-2ED4-4D48-823A-3E4E0F265D38@nicksdot.dev> From: php.lists@allenjb.me.uk (AllenJB) This is a multi-part message in MIME format. --------------zL3oZLfbuVo7VDjBj4MqYFXa Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 01/09/2025 11:28, Nick wrote: > Hey there! > > When I try to look into the discussions of older RFCs to find out why > they ended up the way they did, it’s not easy. You hardly can find > them. This is because they are often not referenced in the RFC itself. > > Going forward, would it make sense to make it mandatory to reference > '[Discussion]' and '[Vote]' in the RFC text itself? > > *Cheers* > Nick FYI I can usually find most RFC discussions by searching on https://externals.io for the RFC title To be clear, I would also still encourage RFC authors to add discussion and vote thread links to RFCs. I think it helps people who are not familiar with the RFC process when RFCs are linked outside of the list, such as on Reddit or social media. I'll often add a comment to RFC posts on r/php to link the discussion threads so people can follow the list discussion. Also, some discussions are harder to find when there's many other list discussions that mention the same keywords as the RFC title. Thought: This could potentially be automated with a script that looks for list emails with a RFC link in the body. If the email body contains a RFC link, the subject contains the RFC title and either [Discussion] or [Vote], then add a reference to the linked RFC wiki page. --------------zL3oZLfbuVo7VDjBj4MqYFXa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 01/09/2025 11:28, Nick wrote:
Hey there!

When I try to look into the discussions of older RFCs to find out why they ended up the way they did, it’s not easy. You hardly can find them. This is because they are often not referenced in the RFC itself.

Going forward, would it make sense to make it mandatory to reference '[Discussion]' and '[Vote]' in the RFC text itself?

Cheers
Nick

FYI I can usually find most RFC discussions by searching on https://externals.io for the RFC title

To be clear, I would also still encourage RFC authors to add discussion and vote thread links to RFCs. I think it helps people who are not familiar with the RFC process when RFCs are linked outside of the list, such as on Reddit or social media. I'll often add a comment to RFC posts on r/php to link the discussion threads so people can follow the list discussion.

Also, some discussions are harder to find when there's many other list discussions that mention the same keywords as the RFC title.

Thought: This could potentially be automated with a script that looks for list emails with a RFC link in the body. If the email body contains a RFC link, the subject contains the RFC title and either [Discussion] or [Vote], then add a reference to the linked RFC wiki page.

--------------zL3oZLfbuVo7VDjBj4MqYFXa--