Without a doubt, one of the biggest problems facing Linux (the most distributed and collaborative project in history) is not about security flaws, threats in the code, or potential attacks, but something that many have not noticed and that with each passing day it becomes more of a reality.
Since its inception, the project has depended (for three decades) on the beating of a single heart: Linus Torvalds, the father of Linux. In 1991, he released a small kernel as a hobby, and today, at 56, he remains the ultimate arbiter of what goes into the operating system that underpins the world's infrastructure. But last week, in an act of historical responsibility, the project decided to stop playing Russian roulette with its future.
Without announcements, without press releases, and buried among thousands of lines of C code, the Linux kernel received a different kind of "patch." It doesn't fix a security flaw or improve hardware support. It's a plain text file called "conclave.rst"And its content answers the question that has kept CIOs and system administrators up at night for years: What happens if Linus Torvalds disappears tomorrow?
The end of the taboo: "Our eventual march towards death"
During years, Talking about the Torvalds succession was almost taboo. an exercise in uncomfortable speculation. However, at the Maintainers Summit 2025 held in Tokyo, The community decided to look the abyss head-on. Dan Williams, a veteran Intel engineer and key figure in the Linux Foundation, presented the proposal under a title laden with dark humor: "An encouraging theme linked to our eventual march towards death."
The result is the "Linux Project Continuity Document". This text formalizes what until now was only a thought, an idea, something that can still wait…
This document acknowledges that, although development is decentralized with more than 100 maintenance providers managing their own subsystems, The final funnel is unique: the torvalds/linux.git repository. If the access keys to that repository are lost, or if its guardians are incapacitated, the flow of updates in the digital world could stop.
The 72-Hour Protocol: A Digital “Conclave”
The document is not a will naming an heir. It doesn't say "Greg Kroah-Hartman will be the new king," even though Greg is Linus's right-hand man and the natural successor in everyone's eyes. Instead, The plan establishes an emergency governance algorithm designed to be activated in the event of a catastrophe.
The protocol works like this:
- The Trigger: If the main maintainers cannot or do not want to continue (which includes the famous "Factor Bus" scenario), the $ORGANIZER figure is activated.
- The Organizer: This role automatically falls to the organizer of the last Maintainers Summit or, failing that, to the chairman of the Technical Advisory Board (TAB) of the Linux Foundation.
- The Countdown: The organizer has a strict 72-hour deadline to call an emergency meeting.
- The Conclave: This meeting is not for just anyone. Only the elite keepers who participated in the last summit are invited (or those selected by the TAB if there was no recent summit).
- The Decision: This select group is responsible for deciding the repository's future: they can elect a new "Benevolent Dictator," establish a board of directors, or define a new management model. The decision must be communicated to the community within two weeks.
The community is not starting from scratch. Ya There is a precedent successful that validates this plan. In 2018, Linus Torvalds temporarily stepped away of the project to work on their social skills and anger management. During that interlude, the release of kernel 4.18 was managed entirely by Greg Kroah-Hartman. The world did not collapse, the servers did not stop, and development continued. That episode served as a vital proof of concept: Linux is bigger than Linus.
However, the human factor still matters. In recent conversations, Torvalds has joked with his usual pragmatism:
"My plan seems to be simply 'to live forever'."
He added, with a touch of irony, that his wife also doesn't want him to retire because she couldn't stand having a "boring husband" at home. But behind the jokes lies an inescapable demographic reality. The maintenance community is aging. Gray hair dominates developer conferences, and the need to ensure an orderly transition to a new generation of leaders is now official policy, not just a hallway concern.
With the merging of this document, Linux closes its most critical vulnerability. It's no longer a project dependent on one person's health, but an institution with self-preservation mechanisms. The "Bus Factor" has been patched up.
Source: https://www.theregister.com