linux-kernel - Re: Code of Conduct: Let's revamp it.

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:   Tue, 18 Sep 2018 22:16:31 +0200
From:   Lukas Wunner <lukas@...ner.de>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Chris Mason <clm@...com>, Dan Williams <dan.j.williams@...el.com>,
        Jonathan Corbet <corbet@....net>,
        Olof Johansson <olof@...m.net>,
        Steven Rostedt <rostedt@...dmis.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: Code of Conduct: Let's revamp it.

On Mon, Sep 17, 2018 at 02:24:30PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Sep 17, 2018 at 01:48:52PM +0200, Lukas Wunner wrote:
> > On Sun, Sep 16, 2018 at 12:22:43PM -0700, Linus Torvalds wrote:
> > > +Scope
> > > +=====
> > > +
> > > +This Code of Conduct applies both within project spaces and in public
> > > +spaces when an individual is representing the project or its community.
> > > +Examples of representing a project or community include using an
> > > +official project e-mail 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.
> > 
> > Seriously though, I read this to know what I need to be aware of but oddly
> > the language of this paragraph says it doesn't apply to me:  I'm not using
> > an official project e-mail address nor an official social media account,
> > nor has anyone appointed me as representative.  I can live with that, I'm
> > just wondering what the benefit of a document is that only seems to apply
> > to a tiny fraction of the community.
> 
> I do not think you are reading the document correctly.  As an example,
> it should cover any emails sent to this list.  That is not a "tiny
> fraction" by my last count :)

You may want to make that more explicit in the document.

The document appears to be geared towards smaller projects with
official project e-mail addresses handed out to a group and it
specifies dos and don'ts for members of that group when they have
their project hat on.

However in the kernel community there's a large continuum with
Linus and those who send him pulls on one end of the spectrum,
and random folks writing on the mailing lists or bugzillas at
the other end.  The further we get to the latter end, the more
menthal gymnastics are necessary (at least for me) to consider
the document applicable to them, given the restrictions laid
out in the "Scope" paragraph.

Just my 2 cents anyway.

Thanks,

Lukas