From: Jan Kara <jack@suse.cz>
To: Jani Nikula <jani.nikula@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org, olof@lxom.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Wed, 26 Sep 2018 11:19:51 +0200 [thread overview]
Message-ID: <20180926091951.GB30730@quack2.suse.cz> (raw)
In-Reply-To: <87k1n8vjef.fsf@intel.com>
On Wed 26-09-18 09:54:00, Jani Nikula wrote:
> On Mon, 24 Sep 2018, Joe Perches <joe@perches.com> wrote:
> > On Mon, 2018-09-24 at 16:15 -0700, James Bottomley wrote:
> >> as a maintainer, I'm happy to try to police
> >> civility by calling adverse behaviours out on the list
> >
> > Good for you, but that's not necessarily something others
> > might want to do. Nor should have to.
>
> I think the only way any code of conduct is ever going to work is
> top-down, with maintainers leading by example, both in terms of
> following and enforcing the CoC. It's not going to work bottom-up, nor
> with everyone always involving the TAB directly. For the most part, it's
> just a matter of explicitly asking people to be civil anyway.
>
> This may well be the biggest reason the "code of conlict" did not
> succeed, despite the large number of acks.
One thing I'm missing: Did "code of conflict" really fail? I find the areas
which I follow (filesystems and surroundings) pretty civil but so they were
even before "code of conflict"... So maybe I miss some events?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2018-09-26 9:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:24 Shuah Khan
2018-09-24 17:51 ` James Morris
2018-09-24 18:11 ` John W. Linville
2018-09-24 19:54 ` Josh Triplett
2018-09-24 20:46 ` Olof Johansson
2018-09-24 22:21 ` Thomas Gleixner
2018-09-25 4:26 ` Daniel Vetter
2018-09-25 6:21 ` Olof Johansson
2018-09-25 8:45 ` Thomas Gleixner
2018-09-25 16:42 ` Daniel Vetter
2018-09-25 20:03 ` Shuah Khan
2018-09-25 6:46 ` Dan Williams
2018-09-24 19:31 ` Jason Cooper
2018-09-26 20:57 ` Mauro Carvalho Chehab
2018-09-24 23:15 ` James Bottomley
2018-09-25 1:35 ` Joe Perches
2018-09-26 6:54 ` Jani Nikula
2018-09-26 9:19 ` Jan Kara [this message]
2018-09-26 9:58 ` Hannes Reinecke
2018-09-26 12:35 ` Mauro Carvalho Chehab
2018-09-26 16:43 ` Mark Brown
2018-09-26 17:03 ` Tim.Bird
2018-09-26 12:30 ` Mauro Carvalho Chehab
2018-09-26 12:51 ` Geert Uytterhoeven
2018-09-26 14:01 ` Shuah Khan
2018-09-25 10:56 ` Jani Nikula
2018-09-25 13:38 ` Jonathan Corbet
2018-09-25 15:22 ` Shuah Khan
2018-09-25 16:51 ` Tim.Bird
2018-09-26 8:04 ` Laura Abbott
2018-09-26 14:47 ` Theodore Y. Ts'o
2018-09-27 8:30 ` Laura Abbott
2018-10-04 16:27 ` James Bottomley
2018-10-05 18:10 ` Shuah Khan
2018-10-06 21:39 ` James Bottomley
2018-10-07 15:27 ` 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=20180926091951.GB30730@quack2.suse.cz \
--to=jack@suse.cz \
--cc=James.Bottomley@hansenpartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lxom.net \
/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