All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tim.Bird@sony.com, josh@joshtriplett.org
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees
Date: Tue, 16 Oct 2018 11:52:58 -0700	[thread overview]
Message-ID: <1539715978.2805.59.camel@HansenPartnership.com> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF80523D65@USCULXMSG01.am.sony.com>

On Tue, 2018-10-16 at 18:38 +0000, Tim.Bird@sony.com wrote:
> > -----Original Message-----
> > From: James Bottomley
> > 
> > On Tue, 2018-10-16 at 11:00 -0700, Josh Triplett wrote:
> > > On Tue, Oct 16, 2018 at 08:13:17AM -0700, James Bottomley wrote:
> > > > On Tue, 2018-10-16 at 10:11 +0200, Daniel Vetter wrote:
> > > > >  And I don't see anyone else from an external community with
> > > > > real experience (or someone who does consulting in this area)
> > > > > invited to fill that gap either.
> > > > 
> > > > I don't buy the narrative that you must be a CoC consultant or
> > > > implementor to make a difference.
> > > 
> > > We typically don't make major changes in a specialized domain
> > > without consulting domain experts, to avoid building a solution
> > > that won't work or ignores well-known issues in that domain. We
> > > wouldn't go off and build a virtualization subsystem without
> > > consulting virtualization experts; we wouldn't build a storage
> > > subsystem without consulting storage experts; we wouldn't hack on
> > > a license without consulting legal experts; the same applies
> > > here.
> > 
> > I notice you carefully cut the part about people who've been active
> > in helping the kernel in this regard already being present;
> 
> I think that characterizing Joshes response as having "carefully cut"
> a section has a little more implication of mal intent that I'd
> prefer.  I think you can reiterate your point about having people
> there that you consider to be domain experts present, without this.

OK, if that was unintentional I apologise for the misinterpretation and
overreaction. I suppose I'm sensitised by the fact that I've seen too
many people spend a huge amount of effort on this for zero recognition.

> > so we do have some domain experts ... plus no external ones have
> > actually been proposed at this point.
> 
> It seemed pretty obvious to me that Daniel was referring to himself
> or someone else from the subsystem (DRM?) that's already adopted
> the CoC.  But a more explicit recommendation (like a candidate name)
> would add clarity to the discussion.
> 
> > We also don't usually listen deferentially to domain experts ...
> > spectre and meltdown would be a case in point here.
> 
> You don't have to be deferential to domain experts to benefit
> from their experience.
> 
> Having said that, I don't think a short face-to-face session is going
> to yield much in the way changes, and the list of invitees was worked
> out already over a long period of time.   And as you stated
> previously there will be other venues (both face-to-face and online)
> to add input to the process.

Agreed, his is why I think the proposed KS/Plumbers session will be far
more important: it's in front of a much wider audience at an open
conference.

James


> Personally I don't see much benefit in changing the invitee list at
> this point, and some dangers.  Not everyone who wants to be there
> can.  That's OK with me.  I'm not invited either.
>  -- Tim
> 
> 
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
> 

  parent reply	other threads:[~2018-10-16 18:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  2:12 [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees Theodore Y. Ts'o
2018-10-16  8:11 ` Daniel Vetter
2018-10-16 15:13   ` James Bottomley
2018-10-16 18:00     ` Josh Triplett
2018-10-16 18:19       ` James Bottomley
2018-10-16 18:38         ` Tim.Bird
2018-10-16 18:46           ` Josh Triplett
2018-10-16 18:57             ` Daniel Vetter
2018-10-16 18:52           ` James Bottomley [this message]
2018-10-16 18:16     ` Mark Brown
2018-10-16 18:36       ` Chris Mason
2018-10-16 19:53 ` [Ksummit-discuss] new topic: regression test infrastructure? (was Draft Maintainer's Summit Agenda and Attendees - ) Christian Borntraeger
2018-10-16 20:51   ` Theodore Y. Ts'o
2018-10-16 21:11     ` Jiri Kosina
2018-10-16 21:14     ` Guenter Roeck
2018-10-16 21:46       ` Theodore Y. Ts'o
2018-10-17  0:08       ` Michael Ellerman
2018-10-17  1:06         ` Tim.Bird
2018-10-17  1:51           ` Shuah Khan

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=1539715978.2805.59.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Tim.Bird@sony.com \
    --cc=josh@joshtriplett.org \
    --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.