ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-discuss@lists.linuxfoundation.org, olof@lxom.net,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Wed, 26 Sep 2018 08:01:17 -0600	[thread overview]
Message-ID: <445e2ebf-e095-712b-fb72-1ded38681963@kernel.org> (raw)
In-Reply-To: <20180926093013.1ff3e2ef@coco.lan>

On 09/26/2018 06:30 AM, Mauro Carvalho Chehab wrote:
> Em Mon, 24 Sep 2018 16:15:02 -0700
> James Bottomley <James.Bottomley@HansenPartnership.com> escreveu:
> 
>> On Mon, 2018-09-24 at 08:24 -0600, Shuah Khan wrote:
> 
>>> What is offensive is a bit more clear. It will be learning curve for
>>> us as a community and I do think we will get there. I believe our
>>> kernel community at large is respectful and helpful.  
>>
>> Actually, reading the above and agreeing with it I think the main
>> problem is that what we're discussing as a Code of Conduct isn't one at
>> all; it's really an anti Harassment policy.  That's why I think it
>> doesn't cover the email reviews and things very well and why we're all
>> concerned that it gives maintainers a load of responsibilities they
>> can't really police.
>>
>> Perhaps we could do with finding a middle ground between the previous
>> code of conflict, which was fairly tailored to our environment but
>> lacked some specifics and the new code of conduct which doesn't seem to
>> be well tailored at all for us.
> 
> Agreed.
> 
>> Perhaps what we're looking for as the middle ground is something based
>> on the Debian code of conduct (obviously with modifications for us):
>>
>> https://www.debian.org/code_of_conduct
> 

Debian code of conduct is to the point and outlines what is expected very
clearly and uses positive language. "Assume good faith" and "Be open"
especially stood out for me as striking the positive and inclusive tone.

> Interesting! They have a separate CoC for mailing lists:
> 
> 	https://www.debian.org/MailingLists/#codeofconduct
> 

Thanks for finding this. This looks good and summarizes "what to do" and "what
not do" that would help us. Probably will need some tweaks to customize it to
suit better for our environment.

thanks,
-- Shuah

  parent reply	other threads:[~2018-09-26 14:01 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
2018-09-26 12:30   ` Mauro Carvalho Chehab
2018-09-26 12:51     ` Geert Uytterhoeven
2018-09-26 14:01     ` Shuah Khan [this message]
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=445e2ebf-e095-712b-fb72-1ded38681963@kernel.org \
    --to=shuah@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=mchehab+samsung@kernel.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