Comment by pydry
6 hours ago
And yet it puts a stop to the tsunami of slop and it's pretty much impossible to prove anything of value was lost.
6 hours ago
And yet it puts a stop to the tsunami of slop and it's pretty much impossible to prove anything of value was lost.
but why? it's a human making the PR and you can shame/ban that human anyway.
I think AI bans are more common in projects where the maintainers are nice people that thoughtfully want to consider each PR and provide a reasoned response if rejected.
That’s only feasible when the people who open PRs are acting in good faith, and control both the quality and volume of PRs to something that the maintainers can realistically (and ought to) review in their 2-3 hours of weekly free time.
Linux is a bit different. Your code can be rejected, or not even looked at in the first place, if it’s not a high quality and desired contribution.
Also, it’s not just about PR quality, but also volume. It’s possible for contributions to be a net benefit in isolation. But most open source maintainers only have an hour or so a week to review PRs and need to prioritize aggressively. People who code with AI agents would benefit themselves to ask “does this PR align with the priorities and time availability of the maintainer?”
For instance, I’m sure we could point AI at many open source projects and tell it to optimize performance. And the agent would produce a bunch of high quality PRs that are a good idea in isolation. But what if performance optimization isn’t a good use of time for a given maintainer’s weekly code review quota?
Sure, maintainers can simply close the PR without a reason if they don’t have time.
But I fear we are taking advantage of nice people, who want to give a reasoned response to every contribution, but simply can’t keep up with the volume that agents can produce.
Volume - things take time to review. If you’re inundated with so many PRs then it’s harder to curate in general
> it's a human making the PR
Is it? Remember when that agent wrote a hit piece about the maintainer because he wouldn't merge it's PR?
That's a different issue actually.
You are treating humans as reasonable actors. They very often are not. On easy to access platforms like github you can have humans just working as intermediaries between LLM and the github. Not actually checking or understanding what they put in a pull request. Banning these people outright with clear rules is much faster and easier than trying to argue with them.
Linux is somewhat harder to contribute to and they already have sufficient barriers in place so they can rely on more reasonable human actors.