From: Shuah Khan <shuah@kernel.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
ksummit-discuss@lists.linuxfoundation.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point
Date: Wed, 17 Oct 2018 09:32:49 -0600 [thread overview]
Message-ID: <eb2ecb2b-7087-d516-b3c5-5e5a09a1f1da@kernel.org> (raw)
In-Reply-To: <1539702015.2805.10.camel@HansenPartnership.com>
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 <konrad.wilk@oracle.com>
> Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
>
> ---
>
> 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
> +<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 (except where
> +required by law).
> +
> Attribution
> ===========
>
>
Acked-by : Shuah Khan <shuah@kernel.org>
thanks,
-- Shuah
prev parent reply other threads:[~2018-10-17 15:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 14:57 [Ksummit-discuss] [PATCH v3 0/3] code of conduct fixes James Bottomley
2018-10-16 14:58 ` [Ksummit-discuss] [PATCH v3 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-17 2:10 ` Frank Rowand
2018-10-17 2:41 ` James Bottomley
2018-10-17 18:49 ` Frank Rowand
2018-10-17 19:07 ` Randy Dunlap
2018-10-17 19:08 ` James Bottomley
2018-10-17 19:53 ` Frank Rowand
2018-10-18 14:56 ` James Bottomley
2018-10-18 19:22 ` Frank Rowand
2018-10-18 19:49 ` Tim.Bird
2018-10-18 19:57 ` James Bottomley
2018-10-18 23:07 ` Frank Rowand
2018-10-17 19:26 ` Alexandre Belloni
2018-10-16 14:59 ` [Ksummit-discuss] [PATCH v3 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-16 15:00 ` [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-17 15:32 ` Shuah Khan [this message]
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=eb2ecb2b-7087-d516-b3c5-5e5a09a1f1da@kernel.org \
--to=shuah@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