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]
Date:   Wed, 17 Oct 2018 09:32:49 -0600
From:   Shuah Khan <shuah@...nel.org>
To:     James Bottomley <James.Bottomley@...senPartnership.com>,
        ksummit-discuss@...ts.linuxfoundation.org
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] [PATCH v3 3/3] code-of-conduct: Add back the
 TAB as the central reporting point

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@...cle.com>
> Reviewed-by: Mauro Carvalho Chehab <mchehab@...nel.org>
> Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Signed-off-by: James Bottomley <James.Bottomley@...senPartnership.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@...ts.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@...nel.org>

thanks,
-- Shuah

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ