From: Mark Brown <broonie@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Draft Maintainer's Summit Agenda and Attendees
Date: Tue, 16 Oct 2018 19:16:28 +0100 [thread overview]
Message-ID: <20181016181628.GK7449@sirena.org.uk> (raw)
In-Reply-To: <1539702797.2805.19.camel@HansenPartnership.com>
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
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
On the one hand I would completely agree that it's entirely possible to
do a good job of implementing a code of conduct without the involvement
of people who are recognized experts in the field. On the other hand
codes of conduct are inevitably partly a marketing and confidence
effort, we could write the most excellent code of conduct possible on
paper but if we can't convince people that we're serious then it's not
going to accomplish a huge amount. This is unfortunately particularly
an issue for the kernel where we have what one might term reputational
challenges to overcome. Having people involved who are widely regarded
as experts should help quite a bit with that, at the very least helping
us explain what we're doing in a way that makes sense to people.
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-16 18:16 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 [this message]
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=20181016181628.GK7449@sirena.org.uk \
--to=broonie@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--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