From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Shuah Khan <shuah@kernel.org>,
ksummit-discuss@lists.linuxfoundation.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
clm@fb.com, dan.j.williams@intel.com,
Jonathan Corbet <corbet@lwn.net>,
olof@lxom.net, rostedt@goodmis.org,
torvalds@linux-foundation.org
Subject: Re: [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it.
Date: Thu, 04 Oct 2018 09:27:55 -0700 [thread overview]
Message-ID: <1538670475.4003.10.camel@HansenPartnership.com> (raw)
In-Reply-To: <cf7638b9-c25d-d47e-f539-192a43268122@kernel.org>
On Mon, 2018-09-24 at 08:24 -0600, Shuah Khan wrote:
> I have been trying to follow various threads on this topic and none
> of them address the review of this patch that went in. There is no
> mistake in the title of this topic. I do consider this topic to be
> more general than limited to Maintainer Summit. Hence, the choice of
> a wider Technical designation.
>
> So I am kicking off a thread to do the review with my comments. I am
> in general agreement with the spirit of this change to the existing
> "Code of Conflict".
Just as an FYI, the Zephyr project recently included the contributor
covenant CoC minus the enforcement clause. They did a standard github
PR for this:
https://github.com/zephyrproject-rtos/zephyr/pull/10356
They note that they may add more enforcement details when the community
agrees on them.
James
next prev parent reply other threads:[~2018-10-04 16:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:24 [Ksummit-discuss] [TECH-TOPIC] Review - Code of Conduct: Let's revamp it 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
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 [this message]
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=1538670475.4003.10.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=clm@fb.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=olof@lxom.net \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.