From: Jens Axboe <axboe@kernel.dk>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>
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 15:20:08 -0600 [thread overview]
Message-ID: <a1cad487-9423-17d8-8cc4-30d03a751843@kernel.dk> (raw)
In-Reply-To: <1536268421.6012.9.camel@HansenPartnership.com>
On 9/6/18 3:13 PM, James Bottomley wrote:
> On Thu, 2018-09-06 at 13:59 -0700, Linus Torvalds 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.
>
> You were the one who mentioned dictators ... I was perfectly happy with
> the bus.
>
>> 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.
>
> OK, so we could still have a plebiscite in Vancouver; we have the room
> and the time still reserved. It could propose a succession plan and
> just present it to you. I admit there's precedent; it's how we did the
> next TAB chair for instance.
>
> 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.
This seems rather hasty to me, I think it would be prudent to establish
a timeline (on both sides?). Unless you are really proposing a coup?
--
Jens Axboe
next prev parent reply other threads:[~2018-09-06 21:20 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 [this message]
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
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=a1cad487-9423-17d8-8cc4-30d03a751843@kernel.dk \
--to=axboe@kernel.dk \
--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