The Linux kernel project has implemented a new protocol to ensure its survival if creator Linus Torvalds becomes unavailable. Titled the Linux Project Continuity Document, the plan outlines an emergency governance process activated in catastrophic scenarios. This measure addresses long-standing concerns about the project's reliance on a single key figure.
The Linux kernel, a cornerstone of global computing infrastructure, has long depended on Linus Torvalds, its founder who released the initial version in 1991 as a hobby project. Now 56, Torvalds serves as the final arbiter for code entering the main repository at torvalds/linux.git. To mitigate risks from this centralization, the project recently integrated a plain text file named conclave.rst, formalizing the Linux Project Continuity Document.
This development emerged from discussions at the Maintainers Summit 2025 in Tokyo. There, Intel engineer Dan Williams, a prominent Linux Foundation member, proposed the framework under the wry title "An encouraging theme linked to our eventual march towards death." The document recognizes that while over 100 maintainers handle subsystems, the project's update flow hinges on Torvalds' repository access.
In a "Bus Factor" emergency—where key maintainers, including Torvalds, cannot continue—the protocol activates an organizer role, assigned to the most recent Maintainers Summit coordinator or the Technical Advisory Board's chair. This organizer must convene an emergency meeting within 72 hours, inviting select participants from the latest summit or TAB appointees. The group then decides the repository's path, such as appointing a new leader or forming a board, with the outcome announced to the community within two weeks.
A 2018 precedent bolsters confidence: Torvalds temporarily withdrew to address personal issues, and Greg Kroah-Hartman, his close collaborator, oversaw kernel 4.18's release without disruption. Torvalds has quipped about his succession, stating, "My plan seems to be simply 'to live forever'." He also noted his wife's reluctance for his retirement, joking she couldn't tolerate a "boring husband" at home.
As the maintainer community ages, this policy shifts Linux from individual dependency to institutional resilience, patching its most human vulnerability.