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  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:   Tue, 23 Oct 2018 10:01:17 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Josh Triplett <josh@...htriplett.org>
Cc:     Joe Perches <joe@...ches.com>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        ksummit-discuss@...ts.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8

On Tue, Oct 23, 2018 at 08:07:50AM +0100, Josh Triplett wrote:
> On Mon, Oct 22, 2018 at 09:16:20PM -0700, Joe Perches wrote:

> > As James Bottomley has suggested multiple times,
> > I'd much rather kernel development use the debian
> > code of conduct verbatim than even this modified one.

> > https://www.debian.org/code_of_conduct

> The Debian code of conduct doesn't do nearly as good a job of addressing
> issues. (Debian also adopted that code of conduct back when such codes
> weren't nearly as well understood or established.) Many people *in*
> Debian, including supporters of their current CoC, have an interest in
> improving it further and/or adopting a more well-established one.

It was recent enough that a lot of the complaints people might have
these days actually got levelled at Debian at the time it was
introduced, and those divergences were for the most part the result of
deliberate decisions.  A big part of this was based on the knowledge
that there's a particular tendency to rules lawyering in parts of the
Debian community, both generally and specifically with the sorts of
behavioural stuff that codes of conduct are designed to address (there's
been examples of people trying to push the limits there before, it's not
just a theoretical concern).  It's definitely an old code of conduct and
could be improved but that's not the only thing going on there.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)

Powered by blists - more mailing lists