ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: <Tim.Bird@sony.com>
To: <broonie@kernel.org>, <jack@suse.cz>
Cc: olof@lxom.net, James.Bottomley@hansenpartnership.com,
	ksummit-discuss@lists.linuxfoundation.org,
	gregkh@linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Wed, 26 Sep 2018 17:03:29 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF80513A85@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20180926164328.GW20825@sirena.org.uk>



> -----Original Message-----
> From: Mark Brown
> 
> On Wed, Sep 26, 2018 at 11:19:51AM +0200, Jan Kara wrote:
> > On Wed 26-09-18 09:54:00, Jani Nikula wrote:
> 
> > > 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?
> 
> There's a few things there.  One is that the name doesn't really convey
> the idea that this is a particularly serious document, and the content
> of the document doesn't do a lot of things that are considered good
> practices for codes of conduct.  A big part of the goal with codes of
> conduct is to send a signal to people outside the community that these
> issues are taken seriously and that they will get backup if there's a
> problem and this stuff meant that it didn't really have those effects,
> people externally didn't take it seriously.

+1
That's why using a "standard" CoC (even as just for a base) has value.
I've heard Greg KH say that people didn't read the Code of Conflict carefully,
and misinterpreted it as encouraging conflict.

  reply	other threads:[~2018-09-26 17:03 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
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 [this message]
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=ECADFF3FD767C149AD96A924E7EA6EAF80513A85@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --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