linux-kernel - Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a9a569566c2771621f170d017ce981dcfff2b1e7.camel@linux.intel.com>
Date:   Tue, 27 Sep 2022 08:59:40 -0700
From:   Kristen Carlson Accardi <kristen@...ux.intel.com>
To:     Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Shuah Khan <skhan@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        LF TAB <tech-board@...ts.linux-foundation.org>
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation
 and practices

On Mon, 2022-09-26 at 17:12 -0600, Jonathan Corbet wrote:
> Kristen Carlson Accardi <kristen@...ux.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@...ux.intel.com>
> > Reviewed-by: Shuah Khan <skhan@...uxfoundation.org>
> > Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.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