From: Olof Johansson <olof@lixom.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus?
Date: Thu, 6 Sep 2018 14:37:32 -0700 [thread overview]
Message-ID: <CAOesGMh8oni1GASydd5K=tN8Q-YkMkSooka5qT4-KUJQFa488A@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFztYx_jjbOCAJcrnej0Vq+S_0a+QZTbkcm9G1fJEn5_pg@mail.gmail.com>
On Thu, Sep 6, 2018 at 1:59 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Sep 6, 2018 at 1:51 PM James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
>>
>> It's happened occasionally, but it's not very traditional. Usually
>> when people do a palace coup replacement, the tumbrels are waiting
>> outside to cart the old dictator off to their sticky end.
>
> This has taken a dark turn.
>
> I do want to point out that I brought the question up last year on the
> spot. I didn't get any reaction then. I was thinking me not being
> around would have been more conducive to discussion. But whatever.
Assuming here that the discussion is NOT about a coup-style immediate
takeover, but instead either:
1) Start sharing more work so that you can scale back sometimes, go
dive without worrying about internet connectivity etc.
or:
2) Prepare for disaster.
I know you have yourself said you don't care what happens in case of
(2) since you won't be around, but I think the best approach is to get
there through (1), if possible.
My suggestion if you want this: Have someone start out doing some of
the simpler mechanics, starting with merging non-controversial fixes
during non-merge window for a cycle or two, and take it from there. It
could even initially be a rotation where a few people try it out for a
bit of time. Some might realize they hate it and should be able to
change their minds without losing face.
I think it was two years ago you proposed having someone else
substitute for a bit, but I don't know if anyone ever volunteered?
You will probably need to approach some of the people you'd trust
enough to do it. Some might find it too intimidating, mistakes are
going to be fairly visible, and I doubt too many will be excited to
volunteer and be turned down, in particular if due to lack of trust.
I think all of that will be easier than finding a new solo maintainer
available at the strike of disaster -- but even if that's what the
goal is, having said person spin up in the same way (i.e. a group of
two for now), seems like the most robust approach.
-Olof
prev parent reply other threads:[~2018-09-06 21:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 19:44 James Bottomley
2018-09-06 19:47 ` Daniel Vetter
2018-09-06 19:51 ` James Bottomley
2018-09-06 20:06 ` Geert Uytterhoeven
2018-09-06 20:35 ` Olof Johansson
2018-09-06 20:45 ` Linus Torvalds
2018-09-06 20:52 ` Olof Johansson
2018-09-08 10:47 ` Mauro Carvalho Chehab
2018-09-08 10:50 ` Thomas Gleixner
2018-09-08 12:21 ` Daniel Vetter
2018-09-09 13:56 ` Laurent Pinchart
2018-09-09 20:05 ` Jiri Kosina
2018-09-06 19:57 ` Linus Torvalds
2018-09-06 20:51 ` James Bottomley
2018-09-06 20:59 ` Linus Torvalds
2018-09-06 21:13 ` James Bottomley
2018-09-06 21:20 ` Jens Axboe
2018-09-06 21:28 ` John W. Linville
2018-09-06 21:34 ` Jens Axboe
2018-09-06 21:41 ` Linus Torvalds
2018-09-06 22:12 ` David Woodhouse
2018-09-06 22:19 ` Linus Torvalds
2018-09-06 22:29 ` James Bottomley
2018-09-06 21:37 ` Olof Johansson [this message]
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='CAOesGMh8oni1GASydd5K=tN8Q-YkMkSooka5qT4-KUJQFa488A@mail.gmail.com' \
--to=olof@lixom.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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