Linux creator and project lead Linus Torvalds apologizes for years of rude behavior, says he is temporarily stepping away from Linux maintenance to get better
From: Linus Torvalds <torvalds@linux-foundation.org> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject …
Context & Ripple Effects
The apology and leave of absence cap a year in which Linus Torvalds' bluntness was on full display — from calling Intel's Spectre and Meltdown fixes "garbage" patches to the routine abrasion that made the kernel tree a difficult place for maintainers. Per the New Yorker's reporting, his decision followed direct questioning about his conduct, not an internal crisis at the Linux Foundation.
The stakes are unusual because Linux is maintained through a hierarchy of subsystem lieutenants with Torvalds as the final merge point — his absence tests whether that structure can absorb the loss of its bottleneck. The arc resolves quickly: he returns with the Linux 4.19 announcement just over a month later, alongside the Code of Conduct whose adoption was itself contested.
First-order effects
- Torvalds hands day-to-day merge decisions to the existing lieutenant structure for the remainder of the 4.19 cycle, making the kernel's patch-acceptance process run without its usual single arbiter.
- Contributors and maintainers who had curtailed or avoided kernel work over abusive review interactions now have explicit acknowledgment from the top that the behavior was wrong.
Second-order effects
- The kernel community's adoption of a formal Code of Conduct becomes the immediate battleground, forcing long-time participants to accept enforced behavioral rules rather than informal norms.
- Other large open source projects face pressure to define succession and conduct standards for their own irreplaceable leaders, since the Linux episode showed both the risk and the survivability of a founder stepping away.
Third-order effects
- Open source governance shifts from personality-dependent leadership toward codified conduct and distributed authority — a pattern echoed years later when Hector Martin resigned from Asahi Linux citing burnout, demanding users, and disagreement with Torvalds' own handling of Rust integration.
- If maintainer burnout and interpersonal friction keep driving exits, corporate-backed foundations and employers take on more of the load of sustaining volunteer-led infrastructure, changing who is accountable for the health of projects like Linux.
The trend: Foundational open source projects are replacing charismatic-single-maintainer cultures with written codes of conduct and layered governance, as Linux's own apology-and-return episode and later maintainer resignations illustrate.