git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ayush Chandekar <ayu.chandekar@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
	redoste <redoste@redoste.xyz>
Subject: Re: [PATCH] SubmittingPatches: allow non-real name contributions
Date: Mon, 07 Jul 2025 07:27:48 +0530	[thread overview]
Message-ID: <2DBEA13C-5E74-4314-9A39-E045A0BC221E@gmail.com> (raw)
In-Reply-To: <xmqqv7o4ajq1.fsf@gitster.g>



Hi,

On 7 July 2025 06:41:02 GMT+05:30, Junio C Hamano <gitster@pobox.com> wrote:
>"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
>> Our submission guidelines require people to use their real name, but
>> this is not always suitable for various reasons.
>> ...
>
>Another thing to consider, which may matter even more in the context
>of SubmittingPatches, is if it is necessary.  If there is a
>requirement, which may or may not be the "real name", that is
>essential to keep DCO enforceable, we will not be able to drop such
>an essential requirement, even if it is "not suitable" for some
>people.  We would have to rather ask these people refrain from
>contributing.
>
>But if a requirment we currently have, like "real name", is not
>necessary and if "known identity" is sufficient, then by all means,
>let's make sure we can loosen the wording to make it "suitable" to
>more people.
>
>> In addition, there are some developers who are so widely known
>> pseudonymously that they have a Wikipedia page with their handle and no
>> real name.  It would seem silly to reject patches from people who are
>> known and respected in their open-source community just because they
>> don't wish to share a real name.
>
>Yup.
>
>> Retain the prohibition on anonymous contributions that the Linux kernel
>> has to ensure that we have some line of provenance to a known (if
>> pseudonymous) author who might be able to respond to questions about it.
>
>Where is this reference to "Linux kernel" come from?  Shouldn't we
>name our own project and adopt this new language for our own rules?
>
>And yes, total anonymity goes directly against provenance traceability,
>so it is not a passive "unfortunately we cannot accept" with regret;
>it is a lot more active and positive "we must not accept an
>anonymous contributions."
>

I want to know how we deal with anonymous contributions. Let's suppose someone creates an internet persona claiming that foo bar is their real name or an alias. They make some contribution and then abandon this persona. So, isn't this effectively an anonymous contribution?

>> I don't claim that this is the best possible wording and I'm open to
>> changing it.   The term "known identity" comes from Linux, but if we
>> need to clarify using different language or otherwise change any part of
>> this up, we can do so.
>
>Thanks for writing this.
>
>>  [[real-name]]
>> -Also notice that a real name is used in the `Signed-off-by` trailer. Please
>> -don't hide your real name.
>> +Please use a known identity in the `Signed-off-by` trailer, since we
>> +unfortunately cannot accept anonymous contributions. It is common to use some
>
>Drop "unfortunately".  We will not accept anonymous contributions.
>It is not like we would wish to if we can but somebody else tells us
>not to.
>
>> +form of your real name. We realize that some contributors are not comfortable
>> +doing so or prefer to contribute under a pseudonym or preferred name and we can
>> +accept your patch either way.
>
>Thanks.
>

Thanks.

Ayush

  reply	other threads:[~2025-07-07  1:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06 16:30 [PATCH] SubmittingPatches: allow non-real name contributions brian m. carlson
2025-07-06 19:36 ` Jacob Keller
2025-07-07  1:11 ` Junio C Hamano
2025-07-07  1:57   ` Ayush Chandekar [this message]
2025-07-07  3:06     ` Theodore Ts'o
2025-07-07  5:28       ` Junio C Hamano
2025-07-10 21:55     ` Jacob Keller
2025-07-07  9:40 ` Phillip Wood
2025-07-07 20:42 ` Jeff King
2025-07-08  7:10   ` Martin Ågren
2025-07-08 22:51     ` Jeff King
2025-07-09 22:42       ` brian m. carlson
2025-07-10  3:46         ` Jeff King
2025-07-10  4:25           ` Junio C Hamano
2025-07-16  0:25 ` [PATCH v2] " brian m. carlson
2025-07-16  4:44   ` Jeff King
2025-07-16  5:47     ` Patrick Steinhardt
2025-07-16 14:41   ` Junio C Hamano

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=2DBEA13C-5E74-4314-9A39-E045A0BC221E@gmail.com \
    --to=ayu.chandekar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=redoste@redoste.xyz \
    --cc=sandals@crustytoothpaste.net \
    /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;
as well as URLs for NNTP newsgroup(s).