When banning AI isn't enough: the governance lesson behind the r/opensource case

In late October 2026, the moderators of r/opensource introduced a blanket ban on artificial intelligence: not just AI-generated content, but any project "made with, for, or aimed at" AI. In the same period, two respected voices in open source each describe — independently, with no direct link to the subreddit's policy — a relationship with AI that is far from outright rejection: Linus Torvalds calls for competent developers who use it as a tool, criticizing the "drive-by patches" of those who don't understand the code they submit; Robert C. Martin, known as "Uncle Bob," has replaced reading his agents' code with code review through automated tests. The contrast, juxtaposed here for editorial reasons and not because the sources link them, shows a community that still has no common line on how to govern AI, while a single moderation policy tries to impose a sharp boundary where, in fact, none yet exists.
What the r/opensource rule actually says
The core of the new rule is in the words of moderator Wolvereness, quoted by The Register: "[...] AI, as it exists today, is incongruent to this Open Source community" — in short, if a project uses AI, is made by AI, or is aimed at AI, it is not welcome on r/opensource.
The ban comes with other clauses. AI-generated translations are banned just as much as original AI content: those who don't write in English are told to look elsewhere, in terms quoted identically by both The Register and Tom's Hardware: "If you don't speak English, you need to find a different community." To be eligible, projects must have at least three contributors, an OSI-approved license, and an existing community with a maintenance track record; anyone posting must have a Reddit account at least one year old. The penalty for breaking the rules is an immediate, permanent ban, with no gradation.
Two positions compared, not an answer to one another
The r/opensource rule is an outright rejection: no distinction between responsible use and abuse, no threshold criterion — the mere presence of AI, in any form, is enough to exclude a project.
It is useful to place this line alongside two public positions held by influential figures in open source, even though these are parallel news episodes that the sources do not connect to the r/opensource affair.
Linus Torvalds, in an interview with Steven Vaughan-Nichols published by The Register on 23 October 2026, neither dismisses AI nor endorses it unconditionally: "I really think we want competent people to use AI as a tool." The problem, for him, is not the tool but those who use it without understanding what it produces: "The 'clueless people using AI' problem is different. I do think we want to discourage that." He adds a distinction worth quoting in full: "I'd argue that these aren't problems with AI itself; they are just problems that are exposed by AI." This is not an unconditional endorsement: it is a selective acceptance, tied to the competence of the person writing the code, not to the technology itself.
Robert C. Martin describes, in public posts from July 2026 picked up and quoted by multiple independent sources, an even more specific practice: he has stopped reading the code written by his AI agents, replacing that reading with automated tests and complexity analysis. In his own words, quoted verbatim by multiple outlets: "My current strategy is to not read any of the code written by my agents. That's the only way I can take advantage of their productivity." Here too, this is not a generic embrace of AI, but a specific change in practice, with a control mechanism — tests — put in place of line-by-line human review.
No source links these two positions to the r/opensource policy: Torvalds and Martin have not commented on the matter, and the policy names neither of them. The juxtaposition is an editorial reading in this piece, not a back-and-forth exchange — but it remains useful to show that the open source community does not speak with one voice on how to govern the adoption of AI.
Why this is a governance problem, not just a moderation one
The most uncomfortable part of the r/opensource rule is not the ban itself, but its enforceability. Wolvereness himself, when asked, admitted there is no objective way to apply it: "There's no 'objective' way to implement this policy." An enforcement criterion that the moderators themselves say they cannot reliably verify — telling human-written text apart from AI-translated text, for instance — is a criterion that produces arbitrariness by construction, not through poor application.
The side effects fall on those with the least bargaining power in the community: non-native English speakers, whom the rule explicitly excludes regardless of whether they use AI or not; solo developers, who don't reach the three-contributor threshold; student or nascent projects, which don't yet have "an existing community and maintenance track record." None of these groups is the rule's stated target, yet all fall within its scope.
A recurring argument among critics of the policy concerns the Linux kernel, often cited as an example of a mainstream project that, in their view, would not pass a consistent test on AI use. This is the critics' argument, not an established fact about the kernel's actual content: no source states that the Linux kernel "contains" AI-generated code in any confirmed way. What is verified is something else: the kernel formalized, in April 2026, rules that allow AI-assisted contributions with a disclosure requirement and human-contributor accountability; in early November 2026 the maintainers dropped that very disclosure requirement. This is a sign of a different regulatory trajectory from r/opensource's — more regulatory, less prohibitionist — not proof that the kernel violates the subreddit's rule.
The community's backlash
The policy triggered widespread backlash, confirmed by third-party sources even though it was not possible to read the individual threads on r/technology and r/SubredditDrama directly (reddit.com refused direct access during verification). The clearest sign of the discontent is the emergence of alternative spaces: not one but two subreddits, r/TrueOpenSource and its twin r/OpenSourceAIAllowed, which the original announcement was later updated to point to. This is a dynamic of "exit" — leaving to build an alternative — rather than "voice," the attempt to fix the rule from within.
The lesson for anyone writing AI policy
A community divided on how to treat AI — shown, in juxtaposition rather than direct response, by the positions of Torvalds and Martin — makes a sharp, admittedly unverifiable enforcement rule even more fragile. The same problem arises, on a different scale, for anyone writing moderation or AI compliance policy in a regulated context: transparency and content-moderation obligations, DSA-style, work when enforcement criteria are stated, verifiable, and backed by a right of appeal. When all three are missing, the result is not a sharper boundary, just a less predictable one.
Closing
An enforcement policy that promises to distinguish what it cannot reliably distinguish produces arbitrariness and excludes those with the least bargaining power — not necessarily the people the rule meant to target. This holds all the more when the very community the policy claims to represent is, in fact, divided over AI: shown by the positions of Torvalds (yes to AI as a tool in the hands of competent developers, no to "drive-by patches") and of Martin (he replaced reading his agents' code with automated tests). It holds for the moderators of a subreddit just as much as for any organization writing an AI policy: enforcement criteria must be stated, verifiable, and backed by a right of appeal before being applied strictly — especially when, as in this case, there is no underlying consensus.
Are your AI policy's criteria actually verifiable?
Stated, verifiable and backed by a right of appeal: that is what separates an enforceable AI policy from a ban that produces arbitrariness. We can help you write and document the criteria before they become a compliance problem.
Let's talk about your AI policy →