The Linux kernel project has finally answered one of the biggest questions gripping the community: what happens if Linus Torvalds is no longer able to lead it?

The " [1]Linux project continuity document ," drafted by Dan Williams, was merged into its documentation last week, just ahead of the release of Linux 6.19-rc7. Notably, the document's path is Documentation/process/conclave.rst.

How and why Linux has thrived after three decades in Kernelland [2]READ MORE

It notes that the kernel development project is "widely distributed, with over 100 maintainers each working to keep changes moving through their own repositories."

But "the final step... is a centralized one where changes are pulled into the mainline repository." And that is "normally done by Linus Torvalds," though "there are others who can do that work when the need arises."

It delicately adds: "Should the maintainers of that repository become unwilling or unable to do that work going forward (including facilitating a transition), the project will need to find one or more replacements without delay."

[3]

So what will happen? The process centers on "$ORGANIZER" who is "the last Maintainer Summit organizer or the current Linux Foundation (LF) Technical Advisory Board (TAB) Chair as a backup."

[4]

[5]

The document says: "Within 72 hours, $ORGANIZER will open a discussion with the invitees of the most recently concluded Maintainers Summit. A meeting of those invitees and the TAB, either online or in-person, will be set as soon as possible in a way that maximizes the number of people who can participate."

In the event of no summit happening in the previous 15 months, the TAB will choose the attendees. Invitees can bring in other maintainers as needed. The meeting will be chaired by $ORGANIZER and will "consider options for the ongoing management of the top-level kernel repository consistent with the expectation that it maximizes the long term health of the project and its community."

[6]

"Next steps" will then be communicated to the broader community through the ksummit@lists.linux.dev mailing list. The Linux Foundation, with guidance from the TAB, will "take the steps necessary to support and implement this plan."

[7]The graying open source community needs fresh blood

[8]Open source maintainers are really feeling the squeeze

[9]Rust for Linux maintainer steps down in frustration with 'nontechnical nonsense'

[10]Open source maintainers underpaid, swamped by security, going gray

The document follows discussion of succession and continuity at the [11]2025 Maintainers Summit . This included what would happen during a "smooth transition" if Torvalds decides it is time to move on, as well as the process "should something happen."

While Torvalds has a firm grip on Linux, as the continuity plan notes, he has himself mused on his own future and the fact the maintainer community, at least for the kernel, is getting grayer.

At the Open Source Summit in 2024, he noted: "Some people are probably still disappointed that I'm still here. I mean, it is absolutely true that kernel maintainers are aging."

He was asked by fellow pioneer Dirk Hohndel of Verizon what the community needs to do to ensure the next generation is ready, "so that in 10, 15, 20, 30 years your role can be handed off to someone else."

[12]

Torvalds replied: "We've always had a lot of people who are very competent and could step up." As for an aging community, he said new people still come in and become main developers within three years. "It's not impossible at all."

And Torvalds is not the only maintainer making plans as the open source community matures. Some projects have, of course, fallen by the wayside over the years. Some remain embedded in the ecosystem, even as their originators and maintainers get older.

One option is handing them over to a foundation. Others like curl originator Daniel Stenberg have remained fiercely independent – with [13]discreet arrangements to pass on their GitHub details when the time comes. ®

Get our [14]Tech Resources



[1] https://github.com/torvalds/linux/commit/102606402f4f5943266160e263c450fdfe4dd981#diff-6c81210e8795b03502471e1435cac0763110f72b823038bd0033eb617c15ab8d

[2] https://www.theregister.com/2025/09/18/three_decades_in_of_linux/

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aXjvQc7BH6GFd-7mXQZ5MAAAAMo&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aXjvQc7BH6GFd-7mXQZ5MAAAAMo&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aXjvQc7BH6GFd-7mXQZ5MAAAAMo&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aXjvQc7BH6GFd-7mXQZ5MAAAAMo&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2024/07/15/opinion_open_source_attract_devs/

[8] https://www.theregister.com/2025/02/16/open_source_maintainers_state_of_open/

[9] https://www.theregister.com/2024/09/02/rust_for_linux_maintainer_steps_down/

[10] https://www.theregister.com/2024/09/18/open_source_maintainers_underpaid/

[11] https://lwn.net/Articles/1050179/

[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/oses&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aXjvQc7BH6GFd-7mXQZ5MAAAAMo&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[13] https://www.bbc.co.uk/news/articles/cly7n2jm5m5o

[14] https://whitepapers.theregister.com/