From: Kristen Carlson Accardi <kristen@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
LF TAB <tech-board@lists.linux-foundation.org>
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices
Date: Tue, 27 Sep 2022 08:59:40 -0700 [thread overview]
Message-ID: <a9a569566c2771621f170d017ce981dcfff2b1e7.camel@linux.intel.com> (raw)
In-Reply-To: <87h70tpw6d.fsf@meer.lwn.net>
On Mon, 2022-09-26 at 17:12 -0600, Jonathan Corbet wrote:
> Kristen Carlson Accardi <kristen@linux.intel.com> writes:
>
> > The Code of Conduct interpretation does not reflect the current
> > practices of the CoC committee or the TAB. Update the documentation
> > to remove references to initial committees and boot strap periods
> > since it is past that time, and note that the this document
> > does serve as the documentation for the CoC committee processes.
>
> Since this takes the TAB's name in vain, they should probably be CC'd
> on
> it; I've added that now.
>
> Thanks,
>
> jon
Thanks Jon,
>
> > Signed-off-by: Kristen Carlson Accardi <kristen@linux.intel.com>
> > Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
> > Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > .../code-of-conduct-interpretation.rst | 24 ++++++++++-----
> > ----
> > 1 file changed, 13 insertions(+), 11 deletions(-)
> >
> > diff --git a/Documentation/process/code-of-conduct-
> > interpretation.rst b/Documentation/process/code-of-conduct-
> > interpretation.rst
> > index 4f8a06b00f60..922e0b547bc3 100644
> > --- a/Documentation/process/code-of-conduct-interpretation.rst
> > +++ b/Documentation/process/code-of-conduct-interpretation.rst
> > @@ -127,10 +127,12 @@ are listed at
> > https://kernel.org/code-of-conduct.html. Members can not
> > access reports made before they joined or after they have left the
> > committee.
> >
> > -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
Eek, I see a small error here - it should either say "The processes the
Code of Conduct committee will use to address reports are varied"
OR
"The process the Code of Conduct committee will use to address reports
is varied"
Perhaps this can be fixed when it is added to a tree, or let me know if
you would like another version.
Thanks,
Kristen
next prev parent reply other threads:[~2022-09-27 15:59 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 [this message]
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
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=a9a569566c2771621f170d017ce981dcfff2b1e7.camel@linux.intel.com \
--to=kristen@linux.intel.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tech-board@lists.linux-foundation.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