From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: NightStrike <nightstrike@gmail.com>
Cc: arsen@aarsen.me, blarsen@redhat.com, pinskia@gmail.com,
gdb@sourceware.org, binutils@sourceware.org
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Fri, 28 Jun 2024 09:08:25 +0300 [thread overview]
Message-ID: <86h6dd4n1i.fsf@gnu.org> (raw)
In-Reply-To: <CAF1jjLu8Fp9M9=CLNbwqWqG6g2YfXScN1YczPR368Fc81hoy8w@mail.gmail.com> (message from NightStrike on Thu, 27 Jun 2024 20:43:05 -0400)
> From: NightStrike <nightstrike@gmail.com>
> Date: Thu, 27 Jun 2024 20:43:05 -0400
> Cc: Arsen Arsenović <arsen@aarsen.me>, blarsen@redhat.com,
> pinskia@gmail.com, gdb@sourceware.org, binutils@sourceware.org
>
> On Tue, Jun 18, 2024 at 7:55 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > > From: Arsen Arsenović <arsen@aarsen.me>
> > > I've, for a long time, avoided contributing to projects with 'legal
> > > routine' requirements (DCO included) due to the implications of sharing
> > > real names.
> >
> > There's no need to share a real name. The assignments on file have
> > quite a few names that are withheld, with only a pseudonym on file.
> > This is a non-issue, for all practical purposes. And, as you point
> > out, using DCOs doesn't change this aspect in any way.
>
> Is this really true? I was denied being able to work on GCC for this
> reason (many years ago, before DCO), because I refused to reveal my
> PII. I pointed out that a real-sounding fake name is no better than a
> fake-sounding fake name, which eventually led to someone (I think Ian)
> explaining that sharing your name is only the first step in validating
> someone's identity. I never pursued it further.
IME, it's true. Like I said, I see in the assignments on file names
of people that are pseudonyms, with real names "withheld".
> Can you please explain how copyright assignments are validated if you
> don't have to share your real name, as opposed to providing a
> real-sounding fake name? This one point has prevented my own
> contributions since 2008; I've limited myself to simply running tests
> and opening PR's.
If you are asking me from the POV of a maintainer of a GNU project
(Emacs), then whether the name is real or not doesn't bother me. As
long as the assignment for "Some Name <some@email.address>" is on
file, I accept the contributions, no questions asked.
If you are asking me from the POV of the FSF copyright-assignment
clerk, the person who deals with the copyright-assignment process,
then I don't know how they do it. I suggest to ask them. They can be
reached at copyright-clerk@fsf.org.
next prev parent reply other threads:[~2024-06-28 6:09 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:52 shaunak saha via Gdb
2024-06-17 12:21 ` Guinevere Larsen via Gdb
2024-06-17 15:00 ` DCO: Was: " Andrew Pinski via Gdb
2024-06-17 15:57 ` Guinevere Larsen via Gdb
2024-06-17 16:07 ` Jan Beulich via Gdb
2024-06-17 16:32 ` Eli Zaretskii via Gdb
2024-06-17 16:37 ` Guinevere Larsen via Gdb
2024-06-17 16:45 ` Eli Zaretskii via Gdb
2024-06-17 18:18 ` Guinevere Larsen via Gdb
2024-06-17 18:24 ` Andrew Pinski via Gdb
2024-06-17 19:57 ` Eli Zaretskii via Gdb
2024-06-17 19:37 ` Eli Zaretskii via Gdb
2024-06-17 19:48 ` Guinevere Larsen via Gdb
2024-06-18 12:25 ` Eli Zaretskii via Gdb
2024-06-27 17:48 ` Thiago Jung Bauermann via Gdb
2024-06-27 19:03 ` Eli Zaretskii via Gdb
2024-06-29 3:27 ` Thiago Jung Bauermann via Gdb
2024-06-17 19:15 ` Arsen Arsenović via Gdb
2024-06-18 11:54 ` Eli Zaretskii via Gdb
2024-06-28 0:43 ` NightStrike via Gdb
2024-06-28 6:08 ` Eli Zaretskii via Gdb [this message]
2024-06-21 13:20 ` Nick Clifton via Gdb
2024-06-23 22:06 ` Tom Tromey
2024-12-02 8:56 ` Luis Machado via Gdb
2025-01-13 17:14 ` Andrew Burgess via Gdb
2025-01-13 17:32 ` Eli Zaretskii via Gdb
2025-01-17 10:37 ` Florian Weimer via Gdb
2025-01-17 10:44 ` Luis Machado via Gdb
2025-01-17 13:01 ` Eli Zaretskii via Gdb
2025-01-21 19:10 ` Guinevere Larsen via Gdb
2025-01-13 17:42 ` Simon Marchi via Gdb
2025-01-14 15:17 ` automated coding style tool (was: RE: DCO: Was: Re: Contributing to gdb) Aktemur, Tankut Baris via Gdb
2025-01-14 17:11 ` automated coding style tool Tom Tromey
2025-01-14 17:14 ` Luis Machado via Gdb
2025-01-14 17:23 ` Simon Marchi via Gdb
2025-01-14 23:04 ` Tom Tromey
2025-01-15 6:03 ` Maciej W. Rozycki
2025-01-18 18:39 ` Tom Tromey
2025-01-22 22:36 ` Maciej W. Rozycki
2025-01-15 10:20 ` Luis Machado via Gdb
2025-01-15 12:24 ` Aktemur, Tankut Baris via Gdb
2025-01-17 13:42 ` Andrew Burgess via Gdb
2025-01-17 15:13 ` Joel Brobecker via Gdb
2025-01-17 15:55 ` Simon Marchi via Gdb
2025-01-17 17:36 ` Phi via Gdb
2025-01-17 19:27 ` Simon Marchi via Gdb
2025-01-18 18:56 ` Tom Tromey
2025-01-20 11:30 ` Luis Machado via Gdb
2025-01-14 17:15 ` Simon Marchi via Gdb
2025-01-14 9:49 ` DCO: Was: Re: Contributing to gdb Luis Machado via Gdb
2025-01-14 13:56 ` Eli Zaretskii via Gdb
2025-01-14 15:10 ` Simon Marchi via Gdb
2025-01-14 15:28 ` Luis Machado via Gdb
2025-01-14 15:47 ` Simon Marchi via Gdb
2025-01-14 16:33 ` Luis Machado via Gdb
2025-01-14 16:42 ` Eli Zaretskii via Gdb
2025-01-15 11:49 ` Mark Wielaard
2025-01-14 16:46 ` Andrew Burgess via Gdb
2025-01-15 11:25 ` Mark Wielaard
2025-01-15 6:20 ` Maciej W. Rozycki
2025-01-15 11:05 ` Mark Wielaard
2025-01-14 15:28 ` Mark Wielaard
2025-01-17 10:42 ` Florian Weimer via Gdb
2025-01-17 13:09 ` Eli Zaretskii via Gdb
2025-01-19 16:37 ` Mark Wielaard
2025-01-27 15:55 ` DCO Bradley M. Kuhn via Gdb
2025-01-27 16:36 ` DCO Krzysztof Siewicz via Gdb
2025-01-27 17:22 ` DCO Guinevere Larsen via Gdb
2025-01-31 19:36 ` DCO Mark Wielaard
2024-06-18 13:32 ` DCO: Was: Re: Contributing to gdb Michael Matz via Gdb
2024-06-19 7:38 ` shaunak saha via Gdb
2024-06-19 12:07 ` Guinevere Larsen via Gdb
2024-06-25 22:27 ` shaunak saha via Gdb
2024-06-26 17:38 ` Tom Tromey
2024-06-28 7:23 ` shaunak saha via Gdb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h6dd4n1i.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=nightstrike@gmail.com \
--cc=pinskia@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox