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: <1543611662.3031.20.camel@HansenPartnership.com>
Date:   Fri, 30 Nov 2018 13:01:02 -0800
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Davidlohr Bueso <dave@...olabs.net>
Cc:     Kees Cook <keescook@...omium.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Amir Goldstein <amir73il@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Daniel Axtens <dja@...ens.net>,
        "David S. Miller" <davem@...emloft.net>,
        Dominik Brodowski <linux@...inikbrodowski.net>,
        Maling list - DRI developers 
        <dri-devel@...ts.freedesktop.org>,
        Eric Dumazet <edumazet@...gle.com>, federico.vaga@...a.pv.it,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Helge Deller <deller@....de>, Jonathan Corbet <corbet@....net>,
        Joshua Kinard <kumba@...too.org>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        linux-ide@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
        Linux Media Mailing List <linux-media@...r.kernel.org>,
        Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
        Linux mtd <linux-mtd@...ts.infradead.org>,
        linux-parisc <linux-parisc@...r.kernel.org>,
        Linux PM list <linux-pm@...r.kernel.org>,
        linux-scsi@...r.kernel.org, matthias.bgg@...il.com,
        Network Development <netdev@...r.kernel.org>,
        nouveau <nouveau@...ts.freedesktop.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Paul Burton <paul.burton@...s.com>,
        Petr Mladek <pmladek@...e.com>, Rob Herring <robh@...nel.org>,
        sean.wang@...iatek.com,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        shannon.nelson@...cle.com, Stefano Brivio <sbrivio@...hat.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        "Tobin C. Harding" <me@...in.cc>, makita.toshiaki@....ntt.co.jp,
        Willem de Bruijn <willemb@...gle.com>,
        Yonghong Song <yhs@...com>, yanjun.zhu@...cle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3

On Fri, 2018-11-30 at 12:55 -0800, Jarkko Sakkinen wrote:
> On Fri, Nov 30, 2018 at 11:56:52AM -0800, Davidlohr Bueso wrote:
> > On Fri, 30 Nov 2018, Kees Cook wrote:
> > 
> > > On Fri, Nov 30, 2018 at 11:27 AM Jarkko Sakkinen
> > > <jarkko.sakkinen@...ux.intel.com> wrote:
> > > > 
> > > > In order to comply with the CoC, replace **** with a hug.
> > 
> > I hope this is some kind of joke. How would anyone get offended by
> > reading technical comments? This is all beyond me...
> 
> Well... Not a joke really but more like conversation starter :-)
> 
> I had 10h flight from Amsterdam to Portland and one of the things
> that I did was to read the new CoC properly.
> 
> This a direct quote from the CoC:
> 
> "Harassment includes the use of abusive, offensive or degrading
> language, intimidation, stalking, harassing photography or recording,
> inappropriate physical contact, sexual imagery and unwelcome sexual
> advances or requests for sexual favors."
> 
> Doesn't this fall into this category?

No because use of what some people consider to be bad language isn't
necessarily abusive, offensive or degrading.  Our most heavily censored
medium is TV and "fuck" is now considered acceptable in certain
contexts on most channels in the UK and EU.

> Your argument is not that great because you could say that from any
> LKML discussion. If you don't like hugging, please propose something
> else
> :-)

The interpretation document also says this:

   ontributions submitted for the kernel should use appropriate
   language. Content that already exists predating the Code of Conduct
   will not be addressed now as a violation.

So that definitely means there should be no hunting down of existing
comments in kernel code.

James

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ