ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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 13:52:50 -0700	[thread overview]
Message-ID: <CAOesGMjPeSXE+TTT33wU1cMwhJp78sKK0i9RsR7CrHmFWoD=dw@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFypAzKSYGxLT=RervWLw28GRr_F2dHNhScBpy_8v6c3gg@mail.gmail.com>

On Thu, Sep 6, 2018 at 1:45 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Sep 6, 2018 at 1:35 PM Olof Johansson <olof@lixom.net> wrote:
>>
>> I'd argue that having a group would be substantially more robust,
>> especially since the pool of people are likely to come from industry
>> and not just LF. We're all pretty good at leaving company politics and
>> influence out of our community work, but it's still desirable to have
>> a bit of balance in the higher maintainer roles.
>
> I think the groups mostly have worked well, but I don't believe in
> that "balance" notion at all.
>
> Because I think *the* most important issue would be that the group
> maintainers trust each other, not that they come from different areas
> in industry.
>
> Of course, outside people would have to trust that group too, but
> trust within the group is I think the most important part by far.

Yeah, I was mostly thinking of outside optics than intra-group dynamics.

For arm-soc it was something that was explicitly considered, Linaro
was just then spinning up and it was important to not give the
impression that companies had to join Linaro to get attention and
equal treatment from the maintainers (and, of course, couldn't apply
pressure to maintainers through membership).

And on a day to day basis it works well. We rarely hit cases where we
send conflicting or contradicting feedback or requests, and if we do,
the later-arriving party either yields or we hash it out quickly. It's
mostly been the case of the former. And yes, trust is obviously key
within the group, no matter background/employment/representation.


-Olof

  reply	other threads:[~2018-09-06 20:52 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 [this message]
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='CAOesGMjPeSXE+TTT33wU1cMwhJp78sKK0i9RsR7CrHmFWoD=dw@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