git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ayush Chandekar <ayu.chandekar@gmail.com>,
	 "brian m. carlson" <sandals@crustytoothpaste.net>,
	 git@vger.kernel.org,  Jeff King <peff@peff.net>,
	 redoste <redoste@redoste.xyz>
Subject: Re: [PATCH] SubmittingPatches: allow non-real name contributions
Date: Sun, 06 Jul 2025 22:28:48 -0700	[thread overview]
Message-ID: <xmqqbjpwa7sf.fsf@gitster.g> (raw)
In-Reply-To: <20250707030609.GA13852@mit.edu> (Theodore Ts'o's message of "Sun, 6 Jul 2025 23:06:09 -0400")

"Theodore Ts'o" <tytso@mit.edu> writes:

> ... advice and review of lawyers employed or contracted by the Linux
> Foundation.  (The Developers of Certification Origin had quite a lot
> of input for lawyers to make sure it would work in multiple legal
> jourisdictions.)
>
> So for example, it's not just about copyright concerns vis-a-vis
> anonymous contributions.  It's also about OFAC Sanctions[1], since an
> anonymous contributor might be someone working for a Sanctioned Entity
> trying to bypass them.

These are excellent points.  All the more reasons why not just we
cannot but we do not want to take anonymous contributions to protect
ourselves.

Thanks.

  reply	other threads:[~2025-07-07  5:28 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 [this message]
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=xmqqbjpwa7sf.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=redoste@redoste.xyz \
    --cc=sandals@crustytoothpaste.net \
    --cc=tytso@mit.edu \
    /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).