linux-kernel - Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1543615449.3031.32.camel@HansenPartnership.com>
Date:   Fri, 30 Nov 2018 14:04:09 -0800
From:   James Bottomley <James.Bottomley@...senPartnership.com>
To:     Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        David Miller <davem@...emloft.net>
Cc:     dave@...olabs.net, keescook@...omium.org,
        linux-kernel@...r.kernel.org, amir73il@...il.com,
        akpm@...ux-foundation.org, andriy.shevchenko@...ux.intel.com,
        dja@...ens.net, linux@...inikbrodowski.net,
        dri-devel@...ts.freedesktop.org, edumazet@...gle.com,
        federico.vaga@...a.pv.it, geert+renesas@...der.be, deller@....de,
        corbet@....net, kumba@...too.org, linux-doc@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, linux-ide@...r.kernel.org,
        linux-m68k@...ts.linux-m68k.org, linux-media@...r.kernel.org,
        linux-mips@...ux-mips.org, linux-mtd@...ts.infradead.org,
        linux-parisc@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-scsi@...r.kernel.org, matthias.bgg@...il.com,
        netdev@...r.kernel.org, nouveau@...ts.freedesktop.org,
        pabeni@...hat.com, paul.burton@...s.com, pmladek@...e.com,
        robh@...nel.org, sean.wang@...iatek.com,
        sergey.senozhatsky@...il.com, shannon.nelson@...cle.com,
        sbrivio@...hat.com, rostedt@...dmis.org, me@...in.cc,
        makita.toshiaki@....ntt.co.jp, willemb@...gle.com, yhs@...com,
        yanjun.zhu@...cle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3

On Fri, 2018-11-30 at 13:54 -0800, Jarkko Sakkinen wrote:
> On Fri, Nov 30, 2018 at 01:48:08PM -0800, David Miller wrote:
> > From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
> > Date: Fri, 30 Nov 2018 13:44:05 -0800
> > 
> > > On Fri, Nov 30, 2018 at 01:01:02PM -0800, James Bottomley wrote:
> > > > 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.
> > > 
> > > This makes following the CoC extremely hard to a non-native
> > > speaker as
> > > it is not too explicit on what is OK and what is not. I did
> > > through the
> > > whole thing with an eye glass and this what I deduced from it.
> > 
> > It would be helpful if you could explain what part of the language
> > is unclear wrt. explaining how CoC does not apply to existing code.
> > 
> > That part seems very explicit to me.
> 
> Well, now that I re-read it, it was this part to be exact:
> 
> "Maintainers have the right and responsibility to remove, edit, or
> reject comments, commits, code, wiki edits, issues, and other
> contributions that are not aligned to this Code of Conduct, or to ban
> temporarily or permanently any contributor for other behaviors that
> they deem inappropriate, threatening, offensive, or harmful."
> 
> How this should be interpreted?

Firstly, this is *only* about contributions going forward.  The
interpretation document says we don't have to look back into the
repository and we definitely can't remove something from git that's
already been committed.

As a Maintainer, if you feel bad language is inappropriate for your
subsystem then you say so and reject with that reason patches that come
in containing it (suggesting alternative rewordings).  However, your
determination about what is or isn't acceptable in your subsystem isn't
binding on other maintainers, who may have different standards ... this
is identical to what we do with coding, like your insistence on one
line per variable or other subsystem's insistence on reverse christmas
tree for includes ...

James


> I have not really followed the previous CoC discussions as I try to
> always use polite language so I'm sorry if this duplicate.
> 
> /Jarkko
>