From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kristen Carlson Accardi <kristen@linux.intel.com>,
linux-doc@vger.kernel.org, corbet@lwn.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices
Date: Tue, 27 Sep 2022 15:30:42 +0700 [thread overview]
Message-ID: <b48636e7-1da3-bc1c-2f2c-d23e0a419f98@gmail.com> (raw)
In-Reply-To: <20220926211149.2278214-1-kristen@linux.intel.com>
On 9/27/22 04:11, Kristen Carlson Accardi wrote:
> -The initial Code of Conduct Committee consists of volunteer members of
> -the TAB, as well as a professional mediator acting as a neutral third
> -party. The first task of the committee is to establish documented
> -processes, which will be made public.
> +The Code of Conduct Committee consists of volunteer community members
> +appointed by the TAB, as well as a professional mediator acting as a
> +neutral third party. The processes the Code of Conduct committee will
> +use to address reports is varied and will depend on the individual
> +circumstance, however, this file serves as documentation for the
> +general process used.
>
> Any member of the committee, including the mediator, can be contacted
> directly if a reporter does not wish to include the full committee in a
> @@ -141,16 +143,16 @@ processes (see above) and consults with the TAB as needed and
> appropriate, for instance to request and receive information about the
> kernel community.
>
> -Any decisions by the committee will be brought to the TAB, for
> -implementation of enforcement with the relevant maintainers if needed.
> -A decision by the Code of Conduct Committee can be overturned by the TAB
> -by a two-thirds vote.
> +Any decisions regarding enforcement recommendations will be brought to
> +the TAB for implementation of enforcement with the relevant maintainers
> +if needed. A decision by the Code of Conduct Committee can be overturned
> +by the TAB by a two-thirds vote.
>
> At quarterly intervals, the Code of Conduct Committee and TAB will
> provide a report summarizing the anonymised reports that the Code of
> Conduct committee has received and their status, as well details of any
> overridden decisions including complete and identifiable voting details.
>
> -We expect to establish a different process for Code of Conduct Committee
> -staffing beyond the bootstrap period. This document will be updated
> -with that information when this occurs.
> +Because how we interpret and enforce the Code of Conduct will evolve over
> +time, this document will be updated when necessary to reflect any
> +changes.
The grammar LGTM, thanks.
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-09-27 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 21:11 [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices Kristen Carlson Accardi
2022-09-26 23:12 ` Jonathan Corbet
2022-09-27 15:59 ` Kristen Carlson Accardi
2022-09-27 16:03 ` Jonathan Corbet
2022-09-27 8:19 ` Bagas Sanjaya
2022-09-27 8:22 ` Greg Kroah-Hartman
2022-09-27 8:27 ` Bagas Sanjaya
2022-09-27 8:43 ` Greg Kroah-Hartman
2022-09-27 12:08 ` Bagas Sanjaya
2022-09-27 8:30 ` Bagas Sanjaya [this message]
2022-09-29 19:15 ` Jonathan Corbet
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=b48636e7-1da3-bc1c-2f2c-d23e0a419f98@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kristen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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