Chris Hartjes on Nostr: An anonymous coder using LLM tools submitted a huge patch to the PHP project to ...
An anonymous coder using LLM tools submitted a huge patch to the PHP project to implement a new feature. I am not going to link to it because that part is not important. I am not a core language contributor but know people who are. You need to set aside your feelings on LLM’s to understand the issue I am going to talk about.
Despite what people think, I have done community organizing for over a decade. The reason to put in rules and procedures is so that you do not have chaos and overwhelm the organizers.
The PHP project supposedly has a rule that new language features require a Request For Comments (RFC). This submission did not have it.
The absolute, 100% correct thing to do from a community perspective would’ve been to reject the PR and tell them to come back with an RFC. It has nothing to do with the source or the tools used.
Instead, people continue to engage with the PR with a bunch of excuses that, from the perspective of a community organizer, are very unserious.
To be blunt: if you do not insist on RFC’s being the precursor to a discussion of a new language feature then you should not bother having an RFC process.
Published at
2026-03-01 14:10:46 UTCEvent JSON
{
"id": "21d33f5de1e7a5dd4e37ac8942915219047096fe64bfd87893fefc27f97ee3e3",
"pubkey": "3f845e362ae0454258e3876fc252b5e3e8b6a4c78bba108107680f31bb32d8e4",
"created_at": 1772374246,
"kind": 1,
"tags": [
[
"proxy",
"https://yac.grumpy-learning.com/users/grmpyprogrammer/statuses/01KJN1GK68V9CP6W7H9MEDA7YN",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "An anonymous coder using LLM tools submitted a huge patch to the PHP project to implement a new feature. I am not going to link to it because that part is not important. I am not a core language contributor but know people who are. You need to set aside your feelings on LLM’s to understand the issue I am going to talk about.\n\nDespite what people think, I have done community organizing for over a decade. The reason to put in rules and procedures is so that you do not have chaos and overwhelm the organizers.\n\nThe PHP project supposedly has a rule that new language features require a Request For Comments (RFC). This submission did not have it.\n\nThe absolute, 100% correct thing to do from a community perspective would’ve been to reject the PR and tell them to come back with an RFC. It has nothing to do with the source or the tools used.\n\nInstead, people continue to engage with the PR with a bunch of excuses that, from the perspective of a community organizer, are very unserious.\n\nTo be blunt: if you do not insist on RFC’s being the precursor to a discussion of a new language feature then you should not bother having an RFC process.",
"sig": "e90d64b6a7bf46968d43255b2e1da1cbccc5b5ee079cce8da176946a2848deff81bc07f2013faea0e31dff892e2299fb118bda00ed8497987822d275587fef0b"
}