Asahi Linux, the volunteer project that ports Linux to Apple Silicon Macs, announced on 7 November 2026 that every repository will move from MIT to GPL 2.0 or later. The legal step is routine and old releases stay MIT. The dispute around it is harder: the project names no culprit, bans most AI contributions, and its best-known rival says nothing changes for it.
Table of Contents
A permissive license lets anyone copy code, change it and sell the result, and that freedom is the reason people choose it. The MIT license has no mechanism for excluding a bad actor, and the volunteers behind Asahi Linux have decided they can no longer accept that. In a progress report dated 7 November 2026, developer James Calligeros said the project had learned of attempts to take its work and replace it, including unreleased feature code lifted from personal forks and published without credit or “lazily rewritten with LLM assistance”. The project’s answer is to move every repository to the GNU General Public License, version 2 or later.
A YouTube commentary on the change makes three arguments. Asahi can relicense without asking anyone, the GPL will not stop people who already ignore licenses, and Omarchy, the AI-driven Linux distribution many assume is the target, is not affected. The first holds, the second goes too far, and the third rests on the party it concerns. The video is independent commentary that closes with an appeal for viewer donations. No sponsor appears in the transcript, and the presenter admits to not being a lawyer.
The report names no one and shows no evidence
The report’s licensing passage is short, and the part that matters most is what it leaves out. It names no project, no person and no repository, and it offers no date or side-by-side comparison for the copying it describes. It’s FOSS, which covered the announcement the next day, makes the same observation and adds that the report does not explain how existing contributions will be relicensed or whether past contributors agreed. Everything about the alleged laundering rests on Asahi’s own account.
The public record does show two AI-friendly forks. It’s FOSS points to Aurora Silicon, whose Borealis Vulkan driver derives from Asahi’s HoneyKrisp driver, and to Gravity Linux, a Fedora-based distribution forked from Asahi over the project’s stance on language models. The same article says Gravity is open source, sells nothing and credits its AI use openly, so it does not match the report’s description, and it stresses that Asahi named neither fork. The video is right that the announcement is vague. The Omarchy connection comes from viewers and commentators, not from the report.
Old MIT releases stay MIT and the switch needs no vote
The video’s legal claim is that a project can move MIT code to a copyleft license without asking contributors. The sources reviewed support the practical version of that claim. Asahi’s copyright policy requires no contributor license agreement and no copyright assignment, so authors keep their copyright, and contributors certify only that they may submit work under the license named in the file. A Wine developer made the underlying point in February 2002, when that project debated its own change: the existing license already allowed anyone to redistribute Wine under the LGPL at any time. Nothing already released changes. The 1.9.9 release notes for the m1n1 bootloader call it the last release under MIT and say the project will be relicensed under GPL v2, and the Hungarian Linux site HUP stresses that the new terms are not retroactive.
Two limits apply. The sources cite no court ruling, and an OpenBSD developer objected on X on 7 November that prior contributors had seemingly not consented. The project’s own copyright policy page, as read on 11 November 2026, also still tells contributors to use a permissive license such as MIT, so the paperwork lags the announcement.
The AI ban is graded and concealment is the red line
The video calls Asahi’s rule a complete ban on AI. The policy is stricter in tone than in text. It says the project broadly forbids generative AI tooling for material contributions, and enforcement scales with the offense: an LLM-drafted GitHub issue may simply be closed, a contributor who used an LLM to interpret a hypervisor trace may get a first and final warning, and concealed extensive use brings an immediate ban. The stated reasons are ethical and legal. Asahi relies on clean-room reverse engineering, and the policy argues that LLMs, agentic ones above all, risk tainting code with material from outside that process.
This is the real fault line, and it is not the license. DHH, the creator of Omarchy, told It’s FOSS that Omarchy would of course contribute its Apple Silicon work back if Asahi lacked the AI rule. The one-way flow the video describes, Asahi code into AI-assisted forks and nothing back, therefore comes from Asahi’s contribution policy. Neither MIT nor the GPL creates it, and the GPL change does not touch it.
Copyleft closes a door the video says stays open
The video’s weakest point is its conclusion that nothing changes, because people who ignore the MIT license will ignore the GPL too. It’s FOSS agrees on part of this: stripping attribution already violated MIT, whose one real condition is keeping the copyright notice, and the GPL cannot stop a determined violator. What the GPL alters is the payoff. Under MIT, a company can take Asahi code, close it and sell a product legally as long as the notice stays. Under the GPL, anyone distributing a modified version must publish its source, so a closed, paid Apple Silicon distribution built on new Asahi code becomes unlawful, and public source makes copying easier to spot.
That is a real change for a legitimate business and a small one for a covert copier. The video also predicts that Asahi will not litigate. None of the sources reviewed says whether the project plans to enforce anything, so the prediction is unsupported either way. What the report does invoke is Wine in 2002, where the aim was to stop proprietary forks and push companies to contribute upstream. That is a goal about reciprocity, not about catching thieves.
Omarchy says the switch changes nothing for it
Timing makes the Omarchy link hard to dismiss. HUP reports that Omarchy 4.5, which installs natively on several Apple Silicon Macs, appeared on 4 November, three days before Asahi’s report. Asked directly, DHH told It’s FOSS that the change may well be a reaction to Omarchy but is irrelevant, because the Linux kernel is already GPL and Omarchy publishes its kernel patches. In his words, “I don’t see how anything changes at all.” Asahi’s copyright policy backs the first half: code written for another project, the kernel included, must carry that project’s license.
The claim is narrow and checks out as far as it goes. What the sources do not examine is how Omarchy’s MIT-licensed tooling will combine with future GPL components. The “monetising” accusation also invites a look at money. The same interview puts the Omacom Foundation’s pledges above 20 million in its introduction and at about $18.5 million in one question, and it says they include AI tokens from Anthropic, OpenAI and Meta. Neither figure comes from the foundation in the material reviewed, so this article relies on neither.
OpenBSD developers lose a pipeline of drivers
Asahi chose MIT in the first place to bring BSD systems along, and the report concedes that this approach is no longer viable. It’s FOSS notes that OpenBSD’s Apple Silicon support relies on Asahi’s m1n1 bootloader, and quotes OpenBSD developer Bryan Steele accusing the project of “burning bridges for no reason”. The video says BSD projects want nothing to do with the GPL. That is the usual BSD position, but here it is the presenter’s characterisation, and no BSD project says it in the sources reviewed. The cost is real but unmeasured: releases up to m1n1 1.9.9 stay available under MIT, while newer Asahi code will not flow into BSD trees on the same terms.
The 2002 Wine discussion shows that this trade was never free. Developer Steve Langasek described the main reason to convert as ensuring that outside parties contribute at least as much back as the LGPL requires, which also meant anyone who valued unrestricted commercial reuse had a reason to vote no.
A license should match the intent behind it
The video’s best advice is also its least dramatic: choose a license for what you want others to do with your code. The Open Source Definition shows why a permissive license cannot be patched afterwards. Its criteria bar discrimination against persons, groups and fields of endeavor, so applying that definition, a license that excluded AI labs or bad-faith users would no longer count as open source. A maintainer who wants reciprocity has to pick copyleft at the start, as the video says Asahi should have.
For anyone building on Asahi work, the practical rule is date-based. Releases through m1n1 1.9.9 can be used under MIT with the notice kept, and newer code arrives under GPL 2.0 or later, which means publishing the source of any modified version you distribute. Mac owners who just want Linux are unaffected, and the same report says M3 machines now install without the EXPERT flag. The evidence that would change this reading is specific: a named case of copied code with the commits side by side, a clear statement from Asahi on how existing contributions were relicensed, or a BSD project saying it can no longer use the drivers.
Author:
Jan Bielik
CEO & Founder of Webiano Digital & Marketing Agency
This article is an original analysis supported by the sources cited below
Asahi Linux Changed Its License and It’s a BIG Deal
The commentary whose three claims about relicensing, AI use and Omarchy this article tests, taken from the transcript supplied for the video.
Progress Report: Linux 7.3 – Asahi Linux
The project’s own 7 November 2026 announcement of the move to GPL 2.0 or later, including its reasons, the Wine comparison and the absence of any named culprit.
Generative AI (LLM) Policy – Asahi Linux
The text of Asahi’s AI rule, which broadly forbids generative AI for material contributions and scales enforcement from closed issues to immediate bans.
Copyright & Reverse Engineering – Asahi Linux
Asahi’s contribution terms, showing no contributor license agreement, contributors keeping copyright and a permissive-license default that still reads unchanged.
Release m1n1 1.9.9 · AsahiLinux/m1n1
The release notes calling 1.9.9 the last m1n1 release under MIT, with later versions to be relicensed under GPL v2.
Wine license change
A February 2002 Wine developer message saying the old license already allowed redistribution under the LGPL and giving the main reason to convert the repository.
The Open Source Definition
The ten criteria, including the bans on discrimination against persons, groups and fields of endeavor, that limit what an open source license can exclude.
Asahi Linux 7.3 progress report
LWN’s 7 November 2026 post confirming the date and the wording of the licensing passage as it first circulated.
Asahi Linux Drops MIT and Goes Full GPL After AI Tools Were Used to Steal Unreleased Code
Independent coverage from 8 November 2026 covering the unnamed forks, what the GPL changes in practice and the OpenBSD developer’s objection.
“First We Take Manhattan”: DHH on Omarchy, AI, Asahi and Winning the Linux Desktop
DHH’s 10 November 2026 answers on whether the switch affects Omarchy, whether it would contribute back and how its foundation funding is described.
Az Omarchy megjelenése után GPL-re vált az Asahi Linux, vitatható indoklással
A Hungarian critical reading from 9 November 2026 that dates Omarchy 4.5 to 4 November and argues the new license is not retroactive.
| Citing this article? Brief excerpts are welcome. Please credit Webiano.digital, name the author where stated, and include a link to https://webiano.digital and to this original article. Full or substantial republication requires prior written permission. Read our Copyright and Content Use Policy. |
This article was prepared with the assistance of artificial intelligence tools. The content underwent expert human review, and Webiano Digital & Marketing Agency assumes editorial responsibility for its final version and publication.
