From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <James.Bottomley@HansenPartnership.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B419F28BF
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Tue, 16 Oct 2018 15:13:20 +0000 (UTC)
Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com
	[66.63.167.143])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 609C8784
	for <ksummit-discuss@lists.linuxfoundation.org>;
	Tue, 16 Oct 2018 15:13:20 +0000 (UTC)
Message-ID: <1539702797.2805.19.camel@HansenPartnership.com>
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, Theodore Ts'o <tytso@mit.edu>
Date: Tue, 16 Oct 2018 08:13:17 -0700
In-Reply-To: <CAKMK7uHxdmJVAtUDWG-=0-qw9RxaW4bONscmbH4PjDZrgYnBqw@mail.gmail.com>
References: <20181016021254.GA21220@thunk.org>
	<CAKMK7uHxdmJVAtUDWG-=0-qw9RxaW4bONscmbH4PjDZrgYnBqw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees
List-Id: <ksummit-discuss.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/ksummit-discuss/>
List-Post: <mailto:ksummit-discuss@lists.linuxfoundation.org>
List-Help: <mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss>,
	<mailto:ksummit-discuss-request@lists.linuxfoundation.org?subject=subscribe>

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