Comment by DennisL123
9 hours ago
Does the policy fix the issue of many low quality PRs being submitted? Unlikely.
Will it fix a related but different problem? Likely.
9 hours ago
Does the policy fix the issue of many low quality PRs being submitted? Unlikely.
Will it fix a related but different problem? Likely.
The people who submit low quality LLM-generated PRs often don't bother to read the policies first, but at least it will be easier to reject those.
While we surely hope that at least some people will read and honor the policy, of course we know not everyone will. But creating a policy gives us teeth. Currently sending such PR is not disallowed, provided it doesn't fall in the thin area of some previous policies about slop PRs. With this policy, doing it will be escalated to the moderation team. First time you'll get a warning, second time you'll be banned from the project.
The point here if you read contributor comments is mainly to allow people to shut a PR down without having claims of “unfairness” because some other PR wasn’t shut down. These are “moderation policies” in the style of old internet forums, their primary purpose is to clear up ambiguity and make maintainer’s (moderators) lives easer.
The birth of vibe coding has seen interactions on public FOSS projects increasingly reminiscent of the flame wars and moderator hammers of the old forum days. A lot of projects have been behind the curve on preparing and codifying the hammers, probably because no maintainer really wants to be a moderator, but thats where its naturally landed unfortunately.
> probably because no maintainer really wants to be a moderator, but thats where its naturally landed unfortunately.
Yeah this is autistic bunk. If you run an open source project, dealing with people is part and parcel of it, disagreements as well.
1 reply →
Ok but what if their OpenClaw reads it for them