Documentation: Project continuity
PATCH 1/1 Documentation: Project continuity
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
--- Documentation/process/conclave.rst | 41 ++++++++++++++++++++++++++++++ Documentation/process/index.rst | 1 + 2 files changed, 42 insertions(+) create mode 100644 Documentation/process/conclave.rst
Documentation/process/conclave.rst new file +41 -0
@@ -0,0 +1,41 @@ +.. SPDX-License-Identifier: GPL-2.0 + +Linux kernel project continuity +=============================== + +The Linux kernel development project is widely distributed, with over +100 maintainers each working to keep changes moving through their own +repositories. The final step, though, is a centralized one where changes +are pulled into the mainline repository. That is normally done by Linus +Torvalds but, as was demonstrated by the 4.19 release in 2018, there are +others who can do that work when the need arises. + +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. The +process by which that will be done is listed below. $ORGANIZER is the +last Maintainer Summit organizer or the current Linux Foundation (LF) +Technical Advisory Board (TAB) Chair as a backup. + +- 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. + +- If there has been no Maintainers Summit in the last 15 months, the set of + invitees for this meeting will be determined by the TAB. + +- The invitees to this meeting may bring in other maintainers as needed. + +- This meeting, chaired by $ORGANIZER, 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. + +- Within two weeks, a representative of this group will communicate to the + broader community, using the [email protected] mailing list, what + the next steps will be. + +The Linux Foundation, as guided by the TAB, will take the steps +necessary to support and implement this plan.
Documentation/process/index.rst +1 -0
@@ -68,6 +68,7 @@ beyond). stable-kernel-rules management-style researcher-guidelines + conclave Dealing with bugs -----------------
base-commit: e9a6fb0bcdd7609be6969112f3fbfcce3b1d4a7c
Signature · 1 line
2.52.0
Quoted 4 lines · On Fri, 23 Jan 2026 17:22:56 -0800 Dan Williams <[email protected]>…
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
The idea behind this document is interesting, but IMHO it is too optimistic for a contingency plan ;-)
Conceptually, contingency plans are written to overcome all foreseeable bad consequences that might happen. So, it should include backups for each possible bad scenario.
Quoted 25 lines
Cc Linus Torvalds <[email protected]>Co-developed-by Jonathan Corbet <[email protected]>Signed-off-by Jonathan Corbet <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Miguel Ojeda <[email protected]>Reviewed-by Kees Cook <[email protected]>Link https://lwn.net/Articles/1050179/ [1]Signed-off-by Dan Williams <[email protected]>--- Documentation/process/conclave.rst | 41 ++++++++++++++++++++++++++++++ Documentation/process/index.rst | 1 + 2 files changed, 42 insertions(+) create mode 100644 Documentation/process/conclave.rstDocumentation/process/conclave.rst new file +5
-0@@ -0,0 +1,41 @@ +.. SPDX-License-Identifier: GPL-2.0 + +Linux kernel project continuity +=============================== +
Documentation/process/conclave.rst line 15
Quoted 10 lines
Documentation/process/conclave.rst new file +10
-0+The Linux kernel development project is widely distributed, with over +100 maintainers each working to keep changes moving through their own +repositories. The final step, though, is a centralized one where changes +are pulled into the mainline repository. That is normally done by Linus +Torvalds but, as was demonstrated by the 4.19 release in 2018, there are +others who can do that work when the need arises. + +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. The
Perhaps it should mention that the "replacements" can be transitory, e.g. something like:
The maintainer replacements will have their mandates limited to the the period of time where the maintainers are unwilling/unable to voice, if the situation is transitory.
Documentation/process/conclave.rst line 18
Quoted 3 lines
Documentation/process/conclave.rst new file +3
-0+process by which that will be done is listed below. $ORGANIZER is the +last Maintainer Summit organizer or the current Linux Foundation (LF) +Technical Advisory Board (TAB) Chair as a backup.
At the worse "hit-by-a-bus" scenarios, the plan may consider that neither $ORGANIZER nor TAB would exist.
For such scenarios, I would add:
If the $ORGANIZER can't be reached within 72 hours, any participant of the last Maintainer Summits can start the process.
Documentation/process/conclave.rst line 25
Quoted 6 lines
Documentation/process/conclave.rst new file +6
-0+- 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. +
Due to the time between the last Maintainers Summit and the conclave, I would add:
The participants of the meeting shall still be actively contributing with the kernel over the two most recent kernel releases.
Also, it sounds reasonable to define a the minimal number of people for the conclave (let's say 30). If the number is inferior, the criteria would be to pick people from the former year and so on until it reaches the minimal threshold.
Documentation/process/conclave.rst line 27
Quoted 2 lines
Documentation/process/conclave.rst new file +2
-0+- If there has been no Maintainers Summit in the last 15 months, the set of + invitees for this meeting will be determined by the TAB.
I would just drop this paragraph.
This text is meant to prevent any weird situation that might compromise the Kernel future. Making it dependent on having an event that could be controlled by outside forces to have happened in the last xx months sounds a bad idea.
Also, if there were no kernel summit in the last year (*), TAB may not have its normal 10 members. It may even have zero elected members on its worse case "hit-by-a-bus" scenario.
Also, on a scenario where TAB won't have enough elected members, a LF contingency plan might be activated, leading to some weird TAB composition, which could be filled with people that don't fill the current criteria and may not understand the Kernel maintainership processes.
For a contingency plan, all of above sounds a bad idea.
So, if we drop this paragraph nominating TAB as backup, the rule would be to pick former Maintainers Summit invitees, which should work properly.
(*) The text says 15 months, but the worse case possible scenario
with one Maintainers Summit per year would be to have one event in, let's say, Jan, 2027 and the next year's one would be in Dec, 2028 (so, 23 months).
Still, if we what happened in 2020, most events were canceled those days, including the Maintainers Summit:
https://events.linuxfoundation.org/archive/2020/linux-kernel-maintainer-summit/
It is not absurd to consider we might have things like that happening in the future.
Quoted 5 lines
Documentation/process/conclave.rst new file +5
-0+ +- The invitees to this meeting may bring in other maintainers as needed. + +- This meeting, chaired by $ORGANIZER, will consider options for the + ongoing management of the top-level kernel repository consistent with
Documentation/process/conclave.rst line 41
Quoted 10 lines
Documentation/process/conclave.rst new file +9
-0+ the expectation that it maximizes the long term health of the project + and its community. + +- Within two weeks, a representative of this group will communicate to the + broader community, using the [email protected] mailing list, what + the next steps will be. + +The Linux Foundation, as guided by the TAB, will take the steps +necessary to support and implement this plan.
This sounds OK, but in this case we probably need a SoB signed by someone that can legally sign in the behalf of The Linux Foundation.
Quoted 13 lines
Documentation/process/index.rst +1
-0@@ -68,6 +68,7 @@ beyond). stable-kernel-rules management-style researcher-guidelines + conclave Dealing with bugs -----------------
Quoted 1 line
base-commit:
e9a6fb0bcdd7609be6969112f3fbfcce3b1d4a7c
Thanks,
Mauro
Greg Kroah-Hartman
maintainerQuoted 8 lines · Mauro Carvalho Chehab
Quoted 4 lines · On Fri, 23 Jan 2026 17:22:56 -0800 Dan Williams <[email protected]>…
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
Quoted 6 lines
The idea behind this document is interesting, but IMHO it is too optimistic for a contingency plan ;-)
Conceptually, contingency plans are written to overcome all foreseeable bad consequences that might happen. So, it should include backups for each possible bad scenario.
That is not the goal here, we aren't going to enumerate all of the potential issues/plans for every possible scenario, that's just impossible and would take forever and likely result in something that is unworkable. This is here to say "these are the steps we will take to form a future plan if something goes wrong with our current one."
thanks,
greg k-h
Quoted 2 lines · Mauro Carvalho Chehab
Also, if there were no kernel summit in the last year (*), TAB may not
Quick note on the TAB elections: while they typically happen during/around the KS/LPC, it is not a hard requirement, and we briefly discussed potentially changing that (unrelated to this document).
So if a KS didn't happen (or was moved to a significantly different time of the year) for some reason, then we would likely need to do elections anyway.
Cheers,
Miguel
Quoted 11 lines · Mauro Carvalho Chehab
Quoted 4 lines
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
The idea behind this document is interesting, but IMHO it is too optimistic for a contingency plan ;-)
Conceptually, contingency plans are written to overcome all foreseeable bad consequences that might happen. So, it should include backups for each possible bad scenario.
I agree with Greg here, that covering each possible scenario is not really realistic an feasible anyway.
I believe that rather than the actual deep details of the plan, it's much more important to have it written that "there is a plan".
I for example know for sure that there are people out there who believe that there is some secret testament hidden somewhere within the depths of Linux Foundation on this topic, and this explicitly clarifies it. Which should be the main prupose, in my view.
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 2 lines · Dan Williams
Document project continuity procedures.
I think I'll just commit this as-is, and directly.
Sure, it could just go through the doc tree, and that would be "standard procedure", but when it comes to something like this, I think it looks better to just have me commit it myself than have me pull it from some other source.
Any future updates from further discussion can then go through the doc tree as normal...
Linus
Jiri Kosina
Reviewed-byQuoted 11 lines · Linus Torvalds
Quoted 1 line
Document project continuity procedures.
I think I'll just commit this as-is, and directly.
Sure, it could just go through the doc tree, and that would be "standard procedure", but when it comes to something like this, I think it looks better to just have me commit it myself than have me pull it from some other source.
Any future updates from further discussion can then go through the doc tree as normal...
FWIW
(or Supported-by:, or whatnot).
Thanks,
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 5 lines · On Fri, 23 Jan 2026 17:22:56 -0800 Dan Williams <[email protected]>…
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
Quoted 8 lines
Cc Linus Torvalds <[email protected]>Co-developed-by Jonathan Corbet <[email protected]>Signed-off-by Jonathan Corbet <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Miguel Ojeda <[email protected]>Reviewed-by Kees Cook <[email protected]>Link https://lwn.net/Articles/1050179/ [1]Signed-off-by Dan Williams <[email protected]>
I thought I sent this out earlier, but anyway...
-- Steve
Quoted 13 lines · Dan Williams
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
Cc Linus Torvalds <[email protected]>Co-developed-by Jonathan Corbet <[email protected]>Signed-off-by Jonathan Corbet <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Miguel Ojeda <[email protected]>Reviewed-by Kees Cook <[email protected]>Link https://lwn.net/Articles/1050179/ [1]Signed-off-by Dan Williams <[email protected]>
Quoted 7 lines
--- Documentation/process/conclave.rst | 41 ++++++++++++++++++++++++++++++ Documentation/process/index.rst | 1 + 2 files changed, 42 insertions(+)create mode 100644
Documentation/process/conclave.rst
Loos good to me.
thanks,
-- Shuah
Quoted 13 lines · Dan Williams
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
Cc Linus Torvalds <[email protected]>Co-developed-by Jonathan Corbet <[email protected]>Signed-off-by Jonathan Corbet <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Miguel Ojeda <[email protected]>Reviewed-by Kees Cook <[email protected]>Link https://lwn.net/Articles/1050179/ [1]Signed-off-by Dan Williams <[email protected]>
Quoted 5 lines
--- Documentation/process/conclave.rst | 41 ++++++++++++++++++++++++++++++ Documentation/process/index.rst | 1 + 2 files changed, 42 insertions(+) create mode 100644 Documentation/process/conclave.rst
Quoted 5 lines · Dan Williams
Document project continuity procedures. This is a plan for a plan for navigating events that affect the forward progress of the canonical Linux repository, torvalds/linux.git. It is a follow-up from Maintainer Summit [1].
Quoted 8 lines
Cc Linus Torvalds <[email protected]>Co-developed-by Jonathan Corbet <[email protected]>Signed-off-by Jonathan Corbet <[email protected]>Reviewed-by Greg Kroah-Hartman <[email protected]>Reviewed-by Miguel Ojeda <[email protected]>Reviewed-by Kees Cook <[email protected]>Link https://lwn.net/Articles/1050179/ [1]Signed-off-by Dan Williams <[email protected]>
FWIW:
Yours,
Linus Walleij