Linus Torvalds shares thoughts on his decision to step away from Linux, the controversy behind the Code of Conduct, and the problems in the Linux community
Linux founder Linus Torvalds has told the BBC that he is seeking professional help to become more empathetic towards fellow developers …
Context & Ripple Effects
Torvalds's BBC interview lands between two milestones already on the record: his September 17 apology for years of rude behavior and the temporary handoff of kernel maintenance, and a New Yorker report saying the step-away followed pointed questions about his conduct rather than pure self-reflection. By telling the BBC he is seeking professional help to become more empathetic, he frames the absence as treatment, not retreat.
The interview also puts him on record about the Code of Conduct controversy and what he calls problems in the Linux community — the first time the project's central figure has addressed the governance fight directly. The arc closes weeks later when he resumes leadership in the Linux 4.19 announcement, though later coverage shows the tension was not fully resolved: Asahi Linux lead Hector Martin's 2025 resignation again cited Torvalds's handling of Rust integration.
First-order effects
- Kernel subsystem maintainers lose their decision-maker for over a month, with patch flow routed around an absent Torvalds until the 4.19 release restores him to the top of the tree.
- The Code of Conduct dispute gains its most consequential voice: the person whose behavior triggered it now publicly endorses the empathy push behind it.
Second-order effects
- Distributions and vendors built on the kernel get a demonstrated succession path — the project survived a month without its founder, lowering perceived key-person risk for anyone shipping Linux at scale.
- Other founder-led projects face pressure to adopt conduct codes and mediation processes preemptively, since the Linux episode made abrasive-maintainer risk a public governance question.
Third-order effects
- If the pattern holds, open-source governance shifts from personality-dependent leadership toward documented conduct processes and distributed maintainer authority — though Hector Martin's later resignation suggests single-maintainer judgment calls remain a live friction point years on.
- Conduct becomes a sustainability issue for critical shared infrastructure: projects underpinning global computing can no longer treat one person's interpersonal style as out of scope for project health.
The trend: Founder-led open source projects are being forced to treat individual conduct and key-person concentration as formal governance risks rather than private matters.