From: Jiri Kosina <jikos@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
corbet@lwn.net, ksummit@lists.linux.dev,
linux-kernel@vger.kernel.org,
tech-board-discuss@lists.linux.dev,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] Documentation: Project continuity
Date: Sat, 24 Jan 2026 21:45:14 +0100 (CET) [thread overview]
Message-ID: <934p49q9-r248-74s5-o936-431oo97o20on@xreary.bet> (raw)
In-Reply-To: <20260124082939.40715e13@foz.lan>
On Sat, 24 Jan 2026, Mauro Carvalho Chehab wrote:
> > 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.
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2026-01-24 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 1:22 Dan Williams
2026-01-24 7:29 ` Mauro Carvalho Chehab
2026-01-24 9:31 ` Greg Kroah-Hartman
2026-01-24 11:17 ` Miguel Ojeda
2026-01-24 20:45 ` Jiri Kosina [this message]
2026-01-24 22:43 ` Linus Torvalds
2026-01-24 22:47 ` Jiri Kosina
2026-01-24 23:58 ` Steven Rostedt
2026-01-26 2:08 ` Shuah
2026-01-26 3:19 ` Julia Lawall
2026-01-27 14:34 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=934p49q9-r248-74s5-o936-431oo97o20on@xreary.bet \
--to=jikos@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=ojeda@kernel.org \
--cc=tech-board-discuss@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox