What Happens If Linus Steps Down? Inside Linux’s New Continuity Plan

Background

The Linux kernel is a massively distributed open‑source project. Over a hundred maintainers each own a subsystem and submit changes to their own trees, while final integration into the mainline repository has traditionally been performed by Linus Torvalds.

Continuity Document

In early 2026 a file titled Linux kernel project continuity was merged into the kernel documentation at Documentation/process/conclave.rst. The document, drafted by maintainer Dan Williams, addresses how the project will continue if the “post‑Linus” situation ever occurs.

Key Principle: Immediate Replacement Process

If a maintainer is unwilling or unable to continue, the project must start a replacement‑selection process without delay.

Who Triggers the Process?

The responsibility falls to the $ORGANIZER —the organizer of the most recent kernel maintainers summit. If that role is vacant, the chair of the Linux Foundation Technical Advisory Board (TAB) automatically assumes the responsibility.

72‑Hour Emergency Timeline

The organizer contacts recent summit participants and TAB members to convene an urgent discussion, either online or offline.

If no summit has been held in the past 15 months, the process is handed directly to TAB, which selects key maintainers to join the discussion.

The meeting focuses on the continued management of the top‑level kernel repository to safeguard the project’s long‑term health.

Within two weeks, a special task group must publish a follow‑up plan to the [email protected] mailing list, outlining concrete next steps. The Linux Foundation will provide support under TAB’s guidance.

Community Consensus (2025 Maintainer Summit)

Linux already possesses “disaster‑response” capabilities: multiple core developers hold merge rights to the mainline tree and stable‑branch maintenance is redundant, eliminating a single point of failure.

It is expected that Linus Torvalds will eventually select a successor and arrange a smooth hand‑over; he has recently signed a new contract with the Linux Foundation and has no immediate plans to step down.

Should an unexpected departure occur, the community agreed that a pre‑defined process is essential to avoid chaotic power struggles.

Decision‑Making Process

When a maintainer steps down, the $ORGANIZER initiates the replacement process. If the organizer position is empty, the TAB chair steps in. This mechanism ensures that kernel evolution does not stall.

Follow‑Up Timeline

After the emergency meeting, a dedicated task force must draft a detailed continuation plan and post it to [email protected] within two weeks. The Linux Foundation, coordinated by TAB, will allocate resources to implement the plan.

References

Documentation file: Documentation/process/conclave.rst in the Linux kernel source tree (https://github.com/torvalds/linux/blob/master/Documentation/process/conclave.rst)

Additional coverage: The Register (https://www.theregister.com/2026/01/27/linux_continuity_plan/), LWN.net (https://lwn.net/Articles/1050179/)