From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, Theodore Ts'o <tytso@mit.edu>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees
Date: Tue, 16 Oct 2018 08:13:17 -0700 [thread overview]
Message-ID: <1539702797.2805.19.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAKMK7uHxdmJVAtUDWG-=0-qw9RxaW4bONscmbH4PjDZrgYnBqw@mail.gmail.com>
On Tue, 2018-10-16 at 10:11 +0200, Daniel Vetter wrote:
> On Tue, Oct 16, 2018 at 4:13 AM Theodore Y. Ts'o <tytso@mit.edu>
> wrote:
> >
> > This is the draft agenda for the Maintainer's Summit which I and
> > the program committee have come up with:
> >
> > 12:00 Lunch / CoC: How did we get here report-out / small group
> > discussion
> > 12:30 Code of Conduct: next steps
>
> CoC is on the agenda and the one subsystem with actual operational
> experience with the exact same CoC is not present.
Given the sudden venue change for the Maintainer summit part, there
were always going to be people who couldn't make it for one reason or
another. The Kernel Summit is still going ahead, as advertised, in
Vancouver and there's a CoC topic proposed there as well and it will be
open to everyone also going to the Linux Plumbers Conference.
> 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
to come out of all the fire and fury levelled at us on social media was
that none of the complainers actually had a recent incident to make an
issue of ... everything was at least two years old or older.
James
next prev parent reply other threads:[~2018-10-16 15:13 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 [this message]
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
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=1539702797.2805.19.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=daniel.vetter@ffwll.ch \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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