AI tools can make it easier to submit code and tests, but Luke Plant argues that this may leave open-source maintainers with more low-quality or poorly considered changes to review. His warning puts the focus on a practical cost of AI-assisted coding: the human effort needed to check and maintain what gets submitted.
Watch Desk analysis
What happened
In “Why I’m calling your contribution ‘slop’”, published on 12 November, Plant argues that AI-generated contributions can increase the review burden on maintainers. He says the lower effort required to produce code or tests can mean more repetitive or unconsidered pull requests, and that maintainers may need to change how they respond to contributors.
Plant’s central standard is that contributions should be made with an understanding that another person may have to maintain every line of code or documentation. The article presents his argument and experience, not a measured estimate of how widespread the problem is.
Why it matters
A pull request is not finished when code appears on screen. Someone still has to decide whether it solves the right problem, fits the project and can be maintained. If AI tools increase the volume of submissions without improving their usefulness, they can shift work from writing code to reviewing it, often onto volunteers.
That makes this more than an argument over whether AI-written code is acceptable. It is a question about the quality and care expected of anyone contributing to shared software. A machine can draft the patch; it cannot take responsibility for the maintainer’s inbox.
Our read
Plant’s most useful point is about ownership: contributors should understand what they submit, whether they used AI or not. That is a stronger standard than trying to police authorship, and a more practical one for projects already coping with limited review time.
But “AI-generated” is not itself proof that a contribution is bad. The useful test is whether the change is considered, explained and maintainable. Projects may need clearer contribution rules, while contributors should expect to defend and revise their work rather than treating a generated draft as someone else’s problem.
What to watch
- Whether open-source projects change contribution guidance or review practices in response to AI-assisted submissions.
- Whether maintainers share evidence about review burden, rather than relying on anecdote alone.
- Whether contributors take responsibility for understanding and supporting code produced with AI tools.
Discussion spark: Should open-source projects require contributors to disclose AI use, or is it better to judge every submission by its quality and maintainability?
Sources and evidence
- Why I’m calling your contribution “slop” (12 November 2026, 10:13 UTC)
Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.