On Thu, Jan 22, 2026 at 1:02 PM Derick Rethans <[email protected]> wrote:
> On Thu, 22 Jan 2026, Nicolas Grekas wrote: > > > Here is a new RFC for you to consider: > > https://wiki.php.net/rfc/promoted_readonly_constructor_reassign > > I read in the linked PR: > > "Team work with Claude Code opus 4.5 💪" > > This makes me instantly want to vote no to this. > I *assume* it was *not* your intention, but the stated message here then is: if you use an LLM to contribute to PHP, keep that information private / do not disclose that information, otherwise you run the risk of getting your contribution rejected due to personal subjective opinion beyond the merits of your contribution. > Code LLMs have been trained on all kinds of open source (and perhaps > proprietary?) software. Open Source nearly always *atleast* has an > "Attribution Required" license. But, these "tools" do not follow these > licenses and the required. > > Therefore, there is no legally possible way to allow AI/LLM > contributions into the PHP source code. > > cheers, > Derick I understand you have a point from the legal perspective, but as a thought experiment we can consider any human-produced contribution potentially tainted with lack of attribution under the same scrutiny, but it wouldn't ever matter. I definitely don't want to be debating in favor of AI use, the accelerated method of burning down the planet or even how OSS is being bombarded by extremely low quality AI-driven contributions. However, I don't think it's in the spirit of OSS, the RFC nor PHP's best interest to debate AI like that on a specific RFC from an author that is known for high quality OSS contributions. Make an RFC and ban any use of AI on the PHP project for all I care, but let's aim to be fair with the RFC being proposed as any other RFC while such a rule/guideline doesn't exist. -- Marco Deleu
