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

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

Message-ID: <20180922000521.u373eysq6dogcdfo@gmail.com>
Date:   Fri, 21 Sep 2018 14:05:21 -1000
From:   Joey Pabalinas <joeypabalinas@...il.com>
To:     "jonsmirl@...il.com" <jonsmirl@...il.com>
Cc:     Theodore Tso <tytso@....edu>, dreamingforward@...il.com,
        fche@...hat.com, riel@...riel.com, ec429@...tab.net,
        Olof Johansson <olof@...om.net>,
        Jonathan Corbet <corbet@....net>,
        lkml <linux-kernel@...r.kernel.org>,
        Joey Pabalinas <joeypabalinas@...il.com>
Subject: Re: Code of Conduct: Let's revamp it.

On Fri, Sep 21, 2018 at 07:31:05PM -0400, jonsmirl@...il.com wrote:
> On Fri, Sep 21, 2018 at 7:17 PM Theodore Y. Ts'o <tytso@....edu> wrote:
> >
> > People can decide who they want to respond to, but I'm going to gently
> > suggest that before people think about responding to a particular
> > e-mail, that they do a quick check using "git log --author=xyzzy@...mple.com"
> > then decide how much someone appears to be a member of the community
> > before deciding how and whether their thoughts are relevant.
> 
> How does this part apply to email addresses used to commit code?
> 
> * Publishing others’ private information, such as a physical or electronic
> address, without explicit permission
> 
> It appears to me that this would conflict with the GPL since the GPL
> granted the right to distribute (or even print it in a book) Linux and
> Linux contains email addresses.  This also seems contradictory with
> the Reply button I used to send this email.

I don't really think email addresses used in patches which are sent,
voluntarily, to a public mailing list are something you can sanely
consider "private information".

> How do you reconcile working on a public project while keeping email
> address secret?

This is a little more delicate, and I admit that I can't really
think of any real solutions for this part...

-- 
Cheers,
Joey Pabalinas

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