Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1354947imm; Wed, 10 Oct 2018 13:11:49 -0700 (PDT) X-Google-Smtp-Source: ACcGV63fc6H1iHp+0NPcxulM3TCb3weiRc7PYSJd9ppIrtx7P58JKm/TbDrsO+EbepB39FyHh4/3 X-Received: by 2002:a62:8559:: with SMTP id u86-v6mr36207108pfd.32.1539202309295; Wed, 10 Oct 2018 13:11:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539202309; cv=none; d=google.com; s=arc-20160816; b=r5+Ex+HEyXUySkDkaVng2X+HSqwZCNspoaS9ysR/9DDAxE0EjjOj5Odc2tSSm8wI2z 7y9upTfkdNTbqMABlueKbhSzPSWNR/dO91Kqhg/xgStCZPga/1ShhDtEvsVvrmNpVl1h CYiIB/zwD5o7u1gUygOQ6oExpJzUoVq8RVBQDXfJp8DPB8laMdjmHOvZPWHcagtjr0JN 5OgYqkMvqsJfsAoJz5R0rdurh7ZKzsljPouE8WDTe65JibHnXN47iszpKny6Fgq4S8hm y8BNs0hvBKHBSSdSyFXzbjcMzkj5mNIFQfh2hPCuuXifiDo4NMeS8ux2FtzaEta0jybb V6Kg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature; bh=7b9Fzl/1TSr/djE/F9LymgUtrx3KlGdhIhBccMmo7sE=; b=I5bv9xTpeJLhqvH2v4pxCZHJmcZDDP4oCUjonj6kNk3VxF3mtg9tXdCni1QnRhBuw1 0rafDYodtRVekcg9v5JYqfpOdH5eN1pX84Q0gukdjUDU1QPNm3e+yn8Oa3wgR+0qBKSF jL6yn+fQOWiKEiKdNvYOm4I39eDljs/2jbT9IsLqomGrtOmnniZmwidnzLMvznoeuf/p Kc+pqLYpdJ0YICQE4GZ2sVnNglOD4yaz05o/zOn+aflVbMZ4D4LivlORiCEzX1rqjoMs DPQEOzytZ9YSWBFeRPt1OGp8i3+PCaNcp2STlZBEupC8IxBcgfxqL6US3FGyC1EpeWGD 2XGA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=ZwN3safe; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n5-v6si25296562plp.186.2018.10.10.13.11.34; Wed, 10 Oct 2018 13:11:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@hansenpartnership.com header.s=20151216 header.b=ZwN3safe; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=hansenpartnership.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727757AbeJKDdZ (ORCPT + 99 others); Wed, 10 Oct 2018 23:33:25 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:57324 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727351AbeJKDdY (ORCPT ); Wed, 10 Oct 2018 23:33:24 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 8A4158EE303; Wed, 10 Oct 2018 13:09:41 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xDmUcAVtI-BT; Wed, 10 Oct 2018 13:09:41 -0700 (PDT) Received: from [153.66.254.194] (unknown [50.35.68.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 3A9568EE0C7; Wed, 10 Oct 2018 13:09:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1539202181; bh=1r4jyqzV7ZgkdcFeG86e5al1FKANymopOwKFL9OFcB4=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=ZwN3safeW0c6+6z8YAtXyEs7XfXHBKXSYcjETR31ElQNWkL53NAbKC/G0HkWGth0l QqOz5kRds0e50uooX0AoInukqHqz3Yl8ROCHofdu9CebHNYhiDzfIUUoZ3ZjTswg6w bbCqtfCSCz7IrTsZ33stVx7XMDOc/IUglv2npMSs= Message-ID: <1539202180.12644.10.camel@HansenPartnership.com> Subject: [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion From: James Bottomley To: ksummit-discuss@lists.linuxfoundation.org Cc: linux-kernel Date: Wed, 10 Oct 2018 13:09:40 -0700 In-Reply-To: <1539202053.12644.8.camel@HansenPartnership.com> References: <1539202053.12644.8.camel@HansenPartnership.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Acked-by: Guenter Roeck Acked-by: Geert Uytterhoeven Reviewed-by: Alan Cox Signed-off-by: James Bottomley --- 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 -. 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 =========== -- 2.13.7