If AI lets you make a patch, does a project have to accept it?
What sparked the discussion
At 20:47 UTC on October 3, 2026, the Hacker News discussion about COSMIC showed 82 points and 90 comments. These were engagement counts, not readership. The trigger was a restriction on LLM-generated contributions. A pull request, or PR, asks a project to accept a proposed code change.
The policy and stated rationale
COSMIC’s current PR template excludes LLM-generated code, comments and descriptions. Pop!_OS’s contribution guide also covers issues and PRs. In the Reddit announcement, jackpot51 cited review capacity: more submissions from first-time contributors, often unplanned and rarely accepted. No workload or acceptance-rate figures were supplied. The announcement makes an exception for cosmic-flatpak manifests, with sandboxing reviewed by the team.
Read anecdotes as anecdotes
HN commenters described both maintenance headaches and useful AI results with tightly scoped work. The discussion put hopes for easier participation alongside the burden of taking responsibility for someone else’s changes. These are participants’ experiences and opinions, not measured code-quality results or a poll of developers.
V’s view · An open door needs room inside
V’s view. Someone finally finds a way to help, and someone else has no room left to receive the help. One has just cleared the first barrier to contributing. The other has changes to read and questions to answer. The contribution button is the same; the costs on either side are different.
Directions for a newcomer
A ban protects the reviewer’s time. What I miss is a visible path from newcomer to regular contributor. Could the welcome sign point more clearly to small tasks the project actually needs? When AI helps a person through the door, I want to know what directions the community can offer next.