Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp804592imm; Wed, 17 Oct 2018 08:34:14 -0700 (PDT) X-Google-Smtp-Source: ACcGV61Yk8s8LlkMXvGEhx+mv+FSKmJ5uUoe8qWzjTKyD0Z3GetD/IDeGwaF5GyaVRXn85kp9830 X-Received: by 2002:a63:2747:: with SMTP id n68-v6mr1887810pgn.443.1539790454323; Wed, 17 Oct 2018 08:34:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539790454; cv=none; d=google.com; s=arc-20160816; b=v/G12t1Y4u4G1+xmhD4vOGm+eca5lsO5N+i/gBIAy6+XuvV7xhGTfddqGvgKraYgBP E1eZIEjL/Ykay1iQRO4SYigmkj+6FvasK4l2LQfmfmGEuiiytdsLbGHRLmonQ371aLhj 7eSdC+OGQWpEYAHFhprXBMsv6lFEFtjeX8Y+igIeAQHjgIn2m0HCqJ6MvRkWBAR+fT25 X7xbO1unqTqD34H+NL7JCZX1o6l9GCey8GAgIHsxICh05Dzs5JzTWNu50R/I/SIin0Q+ uVRUbjqgl3/wPYeiACNwhTFa8Az395187bupuEG2U7O9gAQTBeOcwa2NDHqoyWogftqt 2C5Q== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=sIlQkhLSkMc/XEhe8NeXyF/lu+eGSaN72MfFOftvDFU=; b=kzJcNKXA/JBw7jecbc+BCqOR/Cz337bWlDnPmjKphMYaUQEnOC/QDx0a9c7+faDIoj hWxSeXxr4imlz3AJPdKDRD78SqKMXbhAZrS4aODMGE6hDy5Z8uO8i1wQGqsGZ2+yf7PZ krUawhrjAV3LzuWLF93giJavG+Qs9ptgVy8kls2/7YeqgBHSfzxx3zUhbrHwX53LaEn3 SqQn6rA8ZetZ9kckE1+4yc/dEI8VBUI1y+ohCyosI/35y3PcbjCHPKsttAGz/Tod7h8m CuDGdKW1NCSwjfx9M7pN974/2dwpz3QoL9NjghkRUQxNkC/oG8b9eRg2UHmmddkVEwvh L24Q== ARC-Authentication-Results: i=1; mx.google.com; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a5-v6si17753388pgj.275.2018.10.17.08.33.57; Wed, 17 Oct 2018 08:34:14 -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; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727549AbeJQX3I (ORCPT + 99 others); Wed, 17 Oct 2018 19:29:08 -0400 Received: from mailout.easymail.ca ([64.68.200.34]:40556 "EHLO mailout.easymail.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727048AbeJQX3I (ORCPT ); Wed, 17 Oct 2018 19:29:08 -0400 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 0830021269; Wed, 17 Oct 2018 15:32:54 +0000 (UTC) Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo02-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uoEJf5aIE0U; Wed, 17 Oct 2018 15:32:54 +0000 (UTC) Received: from [192.168.1.87] (c-24-9-64-241.hsd1.co.comcast.net [24.9.64.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 0F1F1211E7; Wed, 17 Oct 2018 15:32:50 +0000 (UTC) Subject: Re: [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point To: James Bottomley , ksummit-discuss@lists.linuxfoundation.org Cc: linux-kernel References: <1539701820.2805.6.camel@HansenPartnership.com> <1539702015.2805.10.camel@HansenPartnership.com> From: Shuah Khan Message-ID: Date: Wed, 17 Oct 2018 09:32:49 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1539702015.2805.10.camel@HansenPartnership.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/16/2018 09:00 AM, James Bottomley wrote: > 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 > =========== > > Acked-by : Shuah Khan thanks, -- Shuah