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 342AE28B8 for ; Tue, 16 Oct 2018 15:00:18 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CF6826E0 for ; Tue, 16 Oct 2018 15:00:17 +0000 (UTC) Message-ID: <1539702015.2805.10.camel@HansenPartnership.com> From: James Bottomley To: ksummit-discuss@lists.linuxfoundation.org Date: Tue, 16 Oct 2018 08:00:15 -0700 In-Reply-To: <1539701820.2805.6.camel@HansenPartnership.com> References: <1539701820.2805.6.camel@HansenPartnership.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: linux-kernel Subject: [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Add a Reporting section where the Enforcement section used to be. The intention is still to debate what should go here, but in the meantime, this gives us back the central reporting point we had in the old code of conflict. Reviewed-by: Konrad Rzeszutek Wilk Reviewed-by: Mauro Carvalho Chehab Acked-by: Geert Uytterhoeven Signed-off-by: James Bottomley --- v2: Added this patch to allay concerns we were stripping the reporting mechanism entirely. v3: Add (where required by law) as a qualifier to the confidentiality requirement --- Documentation/process/code-of-conduct.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Documentation/process/code-of-conduct.rst b/Documentation/process/code-of-conduct.rst index 4dd90987305b..eec768471a4d 100644 --- a/Documentation/process/code-of-conduct.rst +++ b/Documentation/process/code-of-conduct.rst @@ -59,6 +59,17 @@ 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. +Reporting +========= + +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 (except where +required by law). + Attribution =========== -- 2.13.7