ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: 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:41:04 -0700	[thread overview]
Message-ID: <CA+55aFwBx1u4Rq=UjFYk2UNFSt=ek55XbJXJSoszzvEOPrWcEw@mail.gmail.com> (raw)
In-Reply-To: <1536268421.6012.9.camel@HansenPartnership.com>

On Thu, Sep 6, 2018 at 2:13 PM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> However, I really think for an orderly succession plan, you need to be
> part of it rather than having a palace coup which could end up being
> really messy and divisive.  I suspect people treated your proposal last
> year as more of a joke last year because they didn't think you were
> serious.  If you're really serious about doing this, let's try to come
> up with the succession process in Edinburgh in October and see if we
> can run a Maintainer Summit with the new Leadership in Vancouver in
> November.

So I do want to make it clear that it's not like I am all that serious
about it, because I'm perfectly happy to continue to do what I've been
doing for the past almost three decades.

It's not like *I* care about the bus scenario, pretty much by definition.

Honestly, I think the real issue is when *others* have serious and
practical proposals.

In many ways I think that is the real issue: people who feel like
there would be advantages to new models.

The advantages could range from just the "I'd really prefer to work
with somebody else" to more of a "look, Linus isn't getting any
younger, so to make for a smooth transition we should start moving
towards xyz, because then in <N >years we'll be ready".

Regardless, I don't think _my_ opinions matter all that much on this,
and I honestly think some people might be more willing to speak their
mind without me in the room.

And guys, it's not like my ego is all that fragile.  I think people do
know that.  So the only thing I *do* want to be serious about is that
if people actually come up with something that they honestly agree is
better, you don't need to worry about me throwing some hissy-fit, and
"take my ball and go home".

That said, I think we all might have some very real doubts about how
practical it's going to be, and getting people to actually agree on
anything.

What I do *not* want to see is some random flailing discussion while
we're all in the same room. Because I can think of more productive
things to do in Edinburgh, and most of them involve drinking.

So I think people should have some real suggestions before-hand, not
some "let's leave it to an open discussion for the summit itself".

                  Linus

  parent reply	other threads:[~2018-09-06 21:41 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 [this message]
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

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='CA+55aFwBx1u4Rq=UjFYk2UNFSt=ek55XbJXJSoszzvEOPrWcEw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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