git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] SubmittingPatches: allow non-real name contributions

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 7, 2025, 01:11 UTC
Message-ID
<xmqqv7o4ajq1.fsf@gitster.g>
In-Reply-To
<20250706163009.335780-1-sandals@crustytoothpaste.net>
"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.

Show 5 quoted lines
> 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 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.
Show 5 quoted lines
>  [[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.
Previous: Jacob KellerNext: Ayush Chandekar
Message 3 of 18 in “SubmittingPatches: allow non-real name contributions”
  1. SubmittingPatches: allow non-real name contributionsbrian m. carlson, Jul 6, 2025
  2. Jacob KellerJul 6, 2025
  3. Junio C HamanoJul 7, 2025
  4. Ayush ChandekarJul 7, 2025
  5. Theodore Ts'oJul 7, 2025
  6. Junio C HamanoJul 7, 2025
  7. Jacob KellerJul 10, 2025
  8. Phillip WoodJul 7, 2025
  9. Jeff KingJul 7, 2025
  10. Martin ÅgrenJul 8, 2025
  11. Jeff KingJul 8, 2025
  12. brian m. carlsonJul 9, 2025
  13. Jeff KingJul 10, 2025
  14. Junio C HamanoJul 10, 2025
  15. SubmittingPatches: allow non-real name contributionsbrian m. carlson, Jul 16, 2025
  16. Jeff KingJul 16, 2025
  17. Patrick SteinhardtJul 16, 2025
  18. Junio C HamanoJul 16, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.