From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 484506A41 for ; Sun, 7 Oct 2018 17:56:47 +0000 (UTC) Received: from mail-pf1-f194.google.com (mail-pf1-f194.google.com [209.85.210.194]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EA7C7466 for ; Sun, 7 Oct 2018 17:56:46 +0000 (UTC) Received: by mail-pf1-f194.google.com with SMTP id f29-v6so4422567pff.5 for ; Sun, 07 Oct 2018 10:56:46 -0700 (PDT) Sender: Guenter Roeck To: James Bottomley , ksummit-discuss@lists.linuxfoundation.org References: <1538861738.4088.5.camel@HansenPartnership.com> <1538861851.4088.7.camel@HansenPartnership.com> From: Guenter Roeck Message-ID: Date: Sun, 7 Oct 2018 10:56:45 -0700 MIME-Version: 1.0 In-Reply-To: <1538861851.4088.7.camel@HansenPartnership.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Cc: linux-kernel Subject: Re: [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/06/2018 02:37 PM, James Bottomley wrote: > 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. > > Signed-off-by: James Bottomley Acked-by: Guenter Roeck Reasoning: - The TAB was not elected as enforcement agency. - I, as a maintainer, was not consulted when it was decided that I shall be responsible for enforcing the Code of Conduct. Guenter > --- > 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 > -. 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 > =========== > >