From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion
Date: Wed, 10 Oct 2018 23:37:05 -0300 [thread overview]
Message-ID: <20181010233705.12f0f727@coco.lan> (raw)
In-Reply-To: <1539202180.12644.10.camel@HansenPartnership.com>
Em Wed, 10 Oct 2018 13:09:40 -0700
James Bottomley <James.Bottomley@HansenPartnership.com> escreveu:
> Significant concern has been expressed about the responsibilities outlined in
> the enforcement clause of the new code of conduct. Since there is concern
> that this becomes binding on the release of the 4.19 kernel, strip the
> enforcement clauses to give the community time to consider and debate how this
> should be handled.
>
> Note, this patch is expected to be the starting point for a discussion not the
> end point, so there is an expectation that an Enforcement section will be
> added again to our code of conduct once we have sufficient community consensus
> on what it should say.
>
> Fixes: 8a104f8b5867c682 ("Code of Conduct: Let's revamp it.")
> Acked-by: Shuah Khan <shuah@kernel.org>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Reviewed-by: Alan Cox <alan@llwyncelyn.cymru>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
I still think that this series should contain a 4th patch removing
"responsibilities" with that text proposed by Alan.
E. g. instead of:
Maintainers have the right and responsibility to remove, edit, or reject
it should say, instead:
Maintainers should remove, edit or reject
>
> ---
>
> v2: Added additional commit paragraph clarifying we do expect eventually to
> have an enforcement section (as requested by Shuah)
> ---
> Documentation/process/code-of-conduct.rst | 15 ---------------
> 1 file changed, 15 deletions(-)
>
> diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst
> index aa40e34e7785..4dd90987305b 100644
> --- a/Documentation/process/code-of-conduct.rst
> +++ b/Documentation/process/code-of-conduct.rst
> @@ -59,21 +59,6 @@ address, posting via an official social media account, or acting as an appointed
> representative at an online or offline event. Representation of a project may be
> further defined and clarified by project maintainers.
>
> -Enforcement
> -===========
> -
> -Instances of abusive, harassing, or otherwise unacceptable behavior may be
> -reported by contacting the Technical Advisory Board (TAB) at
> -<tab@lists.linux-foundation.org>. All complaints will be reviewed and
> -investigated and will result in a response that is deemed necessary and
> -appropriate to the circumstances. The TAB is obligated to maintain
> -confidentiality with regard to the reporter of an incident. Further details of
> -specific enforcement policies may be posted separately.
> -
> -Maintainers who do not follow or enforce the Code of Conduct in good faith may
> -face temporary or permanent repercussions as determined by other members of the
> -project’s leadership.
> -
> Attribution
> ===========
>
Thanks,
Mauro
next prev parent reply other threads:[~2018-10-11 2:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 20:07 [PATCH v2 0/3] code of conduct fixes James Bottomley
2018-10-10 20:08 ` [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-10 22:17 ` [Ksummit-discuss] " Eric W. Biederman
2018-10-11 2:33 ` Mauro Carvalho Chehab
2018-10-15 20:58 ` Kees Cook
2018-10-10 20:09 ` [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-10 21:04 ` [Ksummit-discuss] " Luck, Tony
2018-10-10 21:19 ` James Bottomley
2018-10-10 21:28 ` Luck, Tony
2018-10-15 21:02 ` Kees Cook
2018-10-11 2:37 ` Mauro Carvalho Chehab [this message]
2018-10-10 20:10 ` [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-10 20:13 ` Alan Cox
2018-10-11 2:30 ` [Ksummit-discuss] " Mauro Carvalho Chehab
2018-10-11 6:50 ` Geert Uytterhoeven
2018-10-10 21:04 ` Konrad Rzeszutek Wilk
2018-10-10 23:23 ` [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes Eric W. Biederman
2018-10-10 23:41 ` Al Viro
2018-10-11 0:00 ` James Bottomley
2018-10-11 3:11 ` Mauro Carvalho Chehab
2018-10-11 10:43 ` Rainer Fiebig
2018-10-11 6:39 ` Tomi Valkeinen
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=20181010233705.12f0f727@coco.lan \
--to=mchehab+samsung@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).