The mods of r/opensource posted new submission rules on Saturday evening, and the first line reads like a manifesto: “If your project uses AI, is made by AI, or is intended for AI, it’s not welcome on r/opensource. AI, as it exists today, is incongruent to this Open Source community.”
I understand the impulse. Anyone who has scrolled a developer forum this year has seen the flood of weekend repos with a generated README, a generated logo and nobody behind them. Moderating that is miserable, unpaid work. But these rules don’t filter out slop. They filter out large parts of open source.
Three bans in one sentence
Look at how much “uses AI, is made by AI, or is intended for AI” covers. “Made by” is the slop problem, and a disclosure rule could have handled it. “Uses” pulls in any project that calls a model anywhere. “Intended for” bans the whole category of open-weight tooling, inference runtimes and agent frameworks, which is arguably where the most active open-source development is happening right now. A forum called r/opensource has decided that a big chunk of current open source is off-topic.
The Linux problem shows how badly the wording holds up. Critics in the thread noted that the kernel now contains some AI-generated code, and Tom’s Hardware points out that kernel maintainers accept AI-assisted contributions as long as they’re disclosed. Read literally, anything built on Linux qualifies for removal. Moderator Wolvereness has said in the comments that enforcement will be selective, with room for things like software whose accessibility features happen to use AI, such as automatic captioning. That makes it worse. A rule the mods admit they’ll apply case by case is a rule that means whatever the mods want on a given day.
The parts nobody should defend
The AI clause is getting the headlines, but the other rules do more damage. Submitted projects now have to be at least a year old, actively maintained, and have multiple contributors. The mods also say they “can no longer field requests asking for maintainers or people to contribute.” So a solo developer with a new project can’t post it, and can’t ask for the help that would get it past the multiple-contributors bar either. Almost every project that later had a community started as one person and a repo nobody had heard of.
Then there’s language. “If you don’t speak English, you need to find a different community,” the post says. The reasoning is that mods can’t tell AI-written text from AI-translated text, and a non-English speaker can’t check whether a translation came out right. That’s an argument for patience with awkward phrasing, not for exclusion. Open source has always run on contributors writing in a second or third language, and plenty of them now use machine translation to do it. Banning them for that throws out real people to make detection easier.
My position is simple: keep the disclosure idea, drop everything else. Ask posters to say whether a project or post was AI-generated, remove the ones that lie, and leave the kernel, the inference engines, the solo devs and the non-native speakers alone.
The community has already started moving. A rival sub, r/trueopensource, popped up within days of the announcement. Whether it keeps an audience once the anger fades, or ends up writing its own rules for the same slop flood, is something the next few months will show.