All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus?
Date: Thu, 06 Sep 2018 12:51:15 -0700	[thread overview]
Message-ID: <1536263475.6012.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAKMK7uFHOP+shcnAdHEEELOth+d3BR0LdUZ9rXdrhYueHdqF9A@mail.gmail.com>

On Thu, 2018-09-06 at 21:47 +0200, Daniel Vetter wrote:
> On Thu, Sep 6, 2018 at 9:44 PM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > Since our fearless leader apparently can't even remember the dates
> > of
> > the only conference he goes to, perhaps now might be a good time to
> > talk about how we'd run an orderly succession process (purely
> > theoretically, of course ...)
> > 
> > I think a vote amongst the Maintainer Summit attendees might be the
> > way
> > to elect a new leader, but others probably have different ideas.
> 
> Why I single leader?
> 
> This group maintainer ship thing ... it  works.

Well, lets talk about that.  I like the single leader model because it
doesn't lead to the cabal cult like the group maintainer model does in
BSD.  However, if we have a plan that can avoid that, I think it would
be a reasonable thing to try out.

I also note that group maintainership seems only to work for you in
DRM; most of the other subsystems seem to have single leader
hierarchical maintainership.

James

  reply	other threads:[~2018-09-06 19:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06 19:44 [Ksummit-discuss] [MAINTAINER TOPIC] Succession Planning: Is It time to Throw Linus Under a Bus? James Bottomley
2018-09-06 19:47 ` Daniel Vetter
2018-09-06 19:51   ` James Bottomley [this message]
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

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=1536263475.6012.5.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=daniel.vetter@ffwll.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.