git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	"Martin Ågren" <martin.agren@gmail.com>,
	git@vger.kernel.org, redoste <redoste@redoste.xyz>
Subject: Re: [PATCH] SubmittingPatches: allow non-real name contributions
Date: Wed, 09 Jul 2025 21:25:51 -0700	[thread overview]
Message-ID: <xmqqzfdc8yeo.fsf@gitster.g> (raw)
In-Reply-To: <20250710034623.GA2066787@coredump.intra.peff.net> (Jeff King's message of "Wed, 9 Jul 2025 23:46:23 -0400")

Jeff King <peff@peff.net> writes:

> On Wed, Jul 09, 2025 at 10:42:58PM +0000, brian m. carlson wrote:
>
>> On 2025-07-08 at 22:51:34, Jeff King wrote:
>> > Yeah, I agree (and didn't know that before; thanks for mentioning). I
>> > think mostly I was just hoping that some of this reasoning and these
>> > pointers would make it into the commit message.
>> > 
>> > The content of the patch looked OK to me, though I do still like the
>> > CNCF wording a bit better.
>> 
>> In case it isn't clear, I'll be sending a v2, probably this weekend with
>> more of this information and some updated wording.
>> 
>> I don't love the CNCF wording because I feel it's too ambiguously
>> worded.  What is the "community"?  The open-source community?  My
>> neighbourhood?  My friend group?  Can a real name be a username or
>> handle that's distinct and unambiguous?  What about communities where
>> people share the same name?  (Debian has, or at least had, two
>> contributors who both have the exact same full legal name and can
>> therefore only be distinguished by handle.)
>> 
>> I also think redefining "real name" in that way is misleading and leads
>> to confusion that might put people off, especially those that are not
>> native English speakers.  I know it's common for lawyers to redefine
>> language to mean something very precise but different from the language
>> that ordinary humans use[0], but that's ultimately dishonest and tends
>> to deceive and we shouldn't do it.  Most people take the phrase "real
>> name" to mean something equivalent to "legal name", so we should use
>> language to describe the requirement that doesn't confuse or mislead
>> people when it's used without further context (such as in a social media
>> post).
>
> Fair points. I think what I liked about it is that it emphasized the
> purpose of the policy:
>
>   The key concern is that your identification is sufficient enough to
>   contact you if an issue were to arise in the future about your
>   contribution.
>
> I also liked the sentence before:
>
>   Your real name is the name you convey to people in the community for
>   them to use to identify you as you.
>
> but I agree that "community" is vague there. I think it mostly means
> "the development community", but I agree that we could perhaps sidestep
> the whole issue by just saying we need some way to be able to identify
> and get in touch with you.
>
>> I'll take some inspiration from the CNCF post and rephrase to make it
>> more approachable in v2.
>
> Great, thank you.

Sounds good.  Thanks, both of you.

  reply	other threads:[~2025-07-10  4:25 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
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 [this message]
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=xmqqzfdc8yeo.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=martin.agren@gmail.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).