At the Open Source Summit Europe 2026 in Prague, the Linux Foundation plastered "AI" across the entire theme wall. The FOSS track chair noted: every exhibitor is talking about how they're using AI, deploying AI, scaling AI, managing AI. But in the same week, a low-profile BSD distribution quietly received a donation that is forcing people to reconsider the open-source map.
The Linux camp's full embrace
The head of Red Hat Global Engineering sent an internal memo a week before the summit, themed "transitioning to an Agentic Software Development Lifecycle" — not a slide deck, but a directive to the entire engineering org. The Debian developers' poll also landed last month: a majority agreed to accept AI-generated contributions, provided the source is disclosed. The Ubuntu Summit has already put AI tooling on the main agenda. The earliest pro-AI signal came from Torvalds himself, who in July made it explicit that "Linux is not an anti-AI project."
This posture isn't empty talk. In the Linux 7.2 merge window, a Sashiko tool open-sourced by a Google engineer — built on Gemini 3.1 Pro — automatically audits patches from the LKML mailing list, and in rc7 alone caught real bugs that human maintainers missed. The 7.2-rc7 merge window absorbed 412 patches in one week, more than double the usual cadence. Torvalds didn't dodge the change — he wrote "the new normal" right into the 7.2-rc7 announcement title.
The anti-AI camp's coordinates
NetBSD, one month after celebrating its 30th birthday in 2024, formally listed ChatGPT, Copilot, and Code Llama outputs as "tainted code," prohibited from commit without prior written approval from core. This rule was written into the repository convention and has never loosened.
At the same time as the Prague summit, NetBSD posted its September fundraising total on Mastodon: $120,282 USD, a project record, far above the $50,000 target. The project's own words: "Naturally, this has completely filled up our donations target bar which was set at $50,000. Time to fund some projects!"
The Register's FOSS desk reporter noticed that at the summit itself, when he mentioned NetBSD, members of the Let's Encrypt team even asked "What's 'net bee ess dee'?" — NetBSD is essentially invisible in the mainstream open-source ecosystem, but the money is flowing from a completely different direction.
The awkward middle ground
OpenBSD holds the most schizophrenic position. Project lead Theo de Raadt has publicly stated that any submitter of AI-generated code lacks the right to license it, because it's impossible to trace which human originally wrote any code that LLMs regurgitate. But tmux — the terminal multiplexer shipped with OpenBSD itself — has already accepted AI-assisted changes inside the tree. When The Register asked de Raadt for comment, he declined.
FreeBSD has moved even more slowly. Its central committee has been debating whether to permit AI-generated code since September 2025, and a full year later there is still no consensus. The three rhetorical currents on the committee — "AI is just a tool," "fall behind and you'll be left behind," "you're probably using the wrong model or the wrong prompt" — cancel each other out, and nobody wants to be the first to put a stake in the ground.
My read
This is not a debate about "whether open source should use AI." It is a route split. The Linux camp bets that "AI is the next generation of compiler/debugger/auditor — refusing it is refusing the next production tool." NetBSD bets that "code is community craft, and machine-generated content will pollute authorship and licensing chains." Each side has been paid for its bet: Linux doubled merge throughput with AI; NetBSD pulled 2.4× its target in donations.
The next 12 months will produce a set of observable signals: whether NetBSD's donations stabilize above $100,000 per month (meaning AI anxiety has become durable purchasing power); whether Debian's first major security incident, after allowing AI code, traces back to an AI-generated commit (deciding the recoil pressure on the "moderate" faction); and whether Red Hat's "Agentic SDLC" memo actually shows up in the product roadmap, or stays a market-facing posture.
So what — the next watershed in the open-source movement isn't a technology argument, it's a values argument: who is willing to keep paying for "code must come from human hands," and who is willing to bet an entire engineering pipeline on "machines take it from here."