Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:128135 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 2F5A51A00BC for ; Sat, 19 Jul 2025 10:35:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1752921229; bh=ECHCai6RQi9HrdDMBKWUnQn3O/ooJTxfeZ+1i+ZcXyw=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=EReXqVW+4ca4lWWIbhEYvVwJtZZK8q6TGR4y+E+OLkpon0ym5lqY8OaTV4ZhXZC5l Kq6aUk3qAaRUtw9nSFbP3zVhQrtCtfY4YsKnbS4k2mrGOmPAybxWPAajqmeJumrmLg 7ptrOuvCcLy1k67M8GM8OsCoix0kYSKAZYC+xtBr+Ornx3cUF7SfuBSd+JHHrdOAPd kgXpIdz+02mxLwvbPg9gu8+HhNv4vdp9DgGhn+KLCA6kDkWCyeu2icFzzwoHHWt+q/ hOijNAQbecB8gzAOvZy6v7MAtHjhx6C0IHcNCaixeLAmINAVIAOsenUTToUb6PzfPc WOjPBqgaSGtlA== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E8C501805E2 for ; Sat, 19 Jul 2025 10:33:48 +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,SPF_HELO_PASS,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 fout-a3-smtp.messagingengine.com (fout-a3-smtp.messagingengine.com [103.168.172.146]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 19 Jul 2025 10:33:38 +0000 (UTC) Received: from phl-compute-05.internal (phl-compute-05.phl.internal [10.202.2.45]) by mailfout.phl.internal (Postfix) with ESMTP id AE8F8EC00D1; Sat, 19 Jul 2025 06:35:24 -0400 (EDT) Received: from phl-imap-05 ([10.202.2.95]) by phl-compute-05.internal (MEProxy); Sat, 19 Jul 2025 06:35:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bottled.codes; h=cc: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=1752921324; x= 1753007724; bh=ECHCai6RQi9HrdDMBKWUnQn3O/ooJTxfeZ+1i+ZcXyw=; b=e CdVQvrPYM1A1CVaEgFsLGjNL1jKNCHG2Br+tfl7zRyGbju4FQOtzx2Wp0dgeep8K YrAFDNhl67d6F/2E/18Vm1qNAqQHKyZPYHPZS/XBrAjyqIPj7ldjWZ+MtdBHOKl6 FV18Cn6Gt0N9vkw6DV03zpNZ+aetb4KTVjiEMRG2+E0vroTwTavvFO+vOE4Mlkxx NhXcM82qu7RQc5/3eOWfgquqSoDpZgaZ1TyVTMz1mdc5Ci1lXgVNvo9YtNK40oKO mVIMGUHFK7fNCbhePXQkhmCeYPXtaiFU3fomyMWQiqX9TmDNTxwOnvWlZq/GoIva C4MBLKA0p7CPYLYAuRrkw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm2; t= 1752921324; x=1753007724; bh=ECHCai6RQi9HrdDMBKWUnQn3O/ooJTxfeZ+ 1i+ZcXyw=; b=eGx+IgODKSvb8hTl5kZsfWMu+U7ilISpD08ZfjJF2epoMRdjLLf nmuzG26IDLc1scA7xkOrgueOvr70vhbhYCfGyuomWPBMajiLHxefGahjWb/5teQh cGrl4fppTnFJ/m13L2+s7K4a8g2Pd8UAZav1rq4idg+stxXWmCjrSYfZaJdnfVq+ rdiUlUdxbH5SShIAhxO7DbbMYgOjCwg9AdmXdScYymYAIUzn+fueely93M00g/LQ oyVhwvqIiac3NL3365W8MmfmpHEGvxut58bjEUUll+Rub7sqlkNVm7MkIcOF8KQW GOjfNuG0+5mtLGDoqd2iKj7xzeJU383KiNg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdeiieduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefoggffhffvvefkjghfufgtsegrtderreertdejnecuhfhrohhmpedftfhosgcunfgr nhguvghrshdfuceorhhosgessghothhtlhgvugdrtghouggvsheqnecuggftrfgrthhtvg hrnhepieeuteehvddvfeejhffgieehleehhedthfefkeejffelgfevvdekudetjeejtddt necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprhhosg essghothhtlhgvugdrtghouggvshdpnhgspghrtghpthhtohepvddpmhhouggvpehsmhht phhouhhtpdhrtghpthhtohepthhimhessggrshhtvghlshhtuhdrsggvpdhrtghpthhtoh epihhnthgvrhhnrghlsheslhhishhtshdrphhhphdrnhgvth X-ME-Proxy: Feedback-ID: ifab94697:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 406FB1820074; Sat, 19 Jul 2025 06:35:24 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 X-ThreadId: T5f4527d1a0d4de24 Date: Sat, 19 Jul 2025 12:32:46 +0200 To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: "php internals" Message-ID: <76059dd0-d27a-4207-9460-658175f54a99@app.fastmail.com> In-Reply-To: <96e0ea70-291e-4f0a-b449-acbaef16c099@bastelstu.be> References: <1e8634d7-ac1a-4025-b4e2-1948aabf5251@app.fastmail.com> <13B58381-AA61-4D38-A688-DD9E367ADE6F@nicksdot.dev> <96e0ea70-291e-4f0a-b449-acbaef16c099@bastelstu.be> Subject: Re: [PHP-DEV] [RFC] [meta] Readonly property hooks Content-Type: multipart/alternative; boundary=54fe0f895630452d878811b44f30b4ec From: rob@bottled.codes ("Rob Landers") --54fe0f895630452d878811b44f30b4ec Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Fri, Jul 18, 2025, at 14:10, Tim D=C3=BCsterhus wrote: > Hi >=20 > Apologies for the belated reply. I was busy with getting my own=20 > implementation wrapped up and the thread was so active that I had=20 > troubles keeping up. Hi Tim, Thanks for taking the time to reply. That said, I would like to address = a concern, not about the content of your message, but the timing. On multiple RFCs, you've joined in once the discussions has wound down a= nd a vote is immeninent. At this point, many participants have assumed t= he key issues are raised and addressed; or at least, reached the point o= f constructive impasse. Reopening settled threads so close to vote tends to disrupt the process.= It forces others to revisit old arguments under time pressure, giving t= he late comments disproportionate visibility, and risks stalling momentu= m. I understand that threads move quickly and schedules vary, but if a conc= ern is important enough to raise, it really helps to do so while the dis= cussions are actively evolving. Otherwise, it becomes difficult to engag= e meaningfully. At a certain point, late feedback stops being helpful and starts to erod= e the trust and rhythm of the process. =E2=80=94 Rob --54fe0f895630452d878811b44f30b4ec Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
On Fri, Jul = 18, 2025, at 14:10, Tim D=C3=BCsterhus wrote:
Hi

Apologies for= the belated reply. I was busy with getting my own 
imple= mentation wrapped up and the thread was so active that I had 
=
troubles keeping up.

Hi Tim,<= /div>

Thanks for taking the time to reply. That said,= I would like to address a concern, not about the content of your messag= e, but the timing.

On multiple RFCs, you've joi= ned in once the discussions has wound down and a vote is immeninent. At = this point, many participants have assumed the key issues are raised and= addressed; or at least, reached the point of constructive impasse.

Reopening settled threads so close to vote tends to= disrupt the process. It forces others to revisit old arguments under ti= me pressure, giving the late comments disproportionate visibility, and r= isks stalling momentum.

I understand that threa= ds move quickly and schedules vary, but if a concern is important enough= to raise, it really helps to do so while the discussions are actively e= volving. Otherwise, it becomes difficult to engage meaningfully.

At a certain point, late feedback stops being helpful = and starts to erode the trust and rhythm of the process.

<= /div>
=E2=80=94 Rob
--54fe0f895630452d878811b44f30b4ec--