Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <CAKON4OxCpCMETfg087wV+ZQ3ssA7eDA8gBSxMYFL9ykVfEGwww@mail.gmail.com>
References: <e223b198-af0e-123d-49bf-fad7e0f9126e@cantab.net>
 <20180919081812.020f19e3@lwn.net> <72dadc76-44fe-ecb5-e142-0a9129082c93@cantab.net>
 <CAOesGMjgo5zwKvsbi8txGQbvFHR2N7xKphzhTSGOrruN3+RC-Q@mail.gmail.com>
 <93b77a9a-12c3-6f7d-d2c3-0e0d7875a28b@cantab.net> <589966d9cd0ddccc88f33fcb7975bb4464be7696.camel@surriel.com>
 <87zhwbj8xe.fsf@redhat.com> <CAMjeLr-mWag=iO=CoNHeK9pkCu4y6vZUp03_zpJOG+e=n85j+g@mail.gmail.com>
 <20180921231545.GC2966@thunk.org> <CAKON4Oy3=7H+9WxzK-xK=T7t7rN7L3_PsJ+cdUWTjiKN=BGSRg@mail.gmail.com>
 <20180922000521.u373eysq6dogcdfo@gmail.com> <CAKON4OxCpCMETfg087wV+ZQ3ssA7eDA8gBSxMYFL9ykVfEGwww@mail.gmail.com>
From:   Max Filippov <jcmvbkbc@gmail.com>
Date:   Mon, 24 Sep 2018 10:43:32 -0700
Message-ID: <CAMo8Bf+ufr_RFtmKMrkCuvObSeGnU2a6L4sDC_LexRcN_a9xaA@mail.gmail.com>
Subject: Re: Code of Conduct: Let's revamp it.
To:     "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc:     joeypabalinas@gmail.com, Theodore Tso <tytso@mit.edu>,
        dreamingforward@gmail.com, fche@redhat.com, riel@surriel.com,
        ec429@cantab.net, Olof Johansson <olof@lixom.net>,
        Jonathan Corbet <corbet@lwn.net>,
        lkml <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Sep 21, 2018 at 5:24 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wr=
ote:
> On Fri, Sep 21, 2018 at 8:05 PM Joey Pabalinas <joeypabalinas@gmail.com> =
wrote:
>> On Fri, Sep 21, 2018 at 07:31:05PM -0400, jonsmirl@gmail.com wrote:
>>> 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...
>
> But... it this bothers you, simply don't use your private, personal
> email address when working on the kernel. Anyone with the skills to
> work on the kernel should know enough to be able to create email
> aliases. No rule says you have to use your real name either.

There is such rule:
  https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html

chapter "Developer=E2=80=99s Certificate of Origin 1.1" says

  then you just add a line saying:
  Signed-off-by: Random J Developer <random@developer.example.org>
  using your real name (sorry, no pseudonyms or anonymous contributions.)

And in general, Developer=E2=80=99s Certificate of Origin
  https://developercertificate.org/

says

  By making a contribution to this project, I certify that:
  ...
(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

--=20
Thanks.
-- Max