ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Mark Brown <broonie@kernel.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees
Date: Tue, 16 Oct 2018 18:36:52 +0000	[thread overview]
Message-ID: <64DFF478-D006-4823-9A52-11550CD4A525@fb.com> (raw)
In-Reply-To: <20181016181628.GK7449@sirena.org.uk>

On 16 Oct 2018, at 14:16, Mark Brown 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.  The kernel communities have been
>> getting better for a while and several people on the invitee list 
>> have
>> had a lot to do with that.  For me, one of the most gratifying things

I hope that maintainers summit and plumbers are just part of our 
continued conversation about all of these issues.  It's really hard to 
setup the perfect set of people in the room when we're still working on 
all of the questions that need to be asked and finding the best set of 
people to work on them.

[ ... ]

>
> One of the things we could end up doing at the meeting is deferring 
> some
> of the decision for mailing list or other discussion which would give 
> a
> space for that to happen.

Strongly agree here.

-chris

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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  2:12 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
2018-10-16 18:16     ` Mark Brown
2018-10-16 18:36       ` Chris Mason [this message]
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=64DFF478-D006-4823-9A52-11550CD4A525@fb.com \
    --to=clm@fb.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox