git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Ayush Chandekar <ayu.chandekar@gmail.com>
Cc: Junio C Hamano <gitster@pobox.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, 6 Jul 2025 23:06:09 -0400	[thread overview]
Message-ID: <20250707030609.GA13852@mit.edu> (raw)
In-Reply-To: <2DBEA13C-5E74-4314-9A39-E045A0BC221E@gmail.com>

On Mon, Jul 07, 2025 at 07:27:48AM +0530, Ayush Chandekar wrote:
> >
> >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."

Well, the SubmittingPatches originally came from the Linux Kernel, and
the policies and procedures that were adopted by the Linux Kernel
comes from a lot of hard won experience which the git project might
want to consider.  In addition, it was also informed with a lot of
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.

[1] https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions

(And note, it's not just about the US Sanctions; there are very
similar, and in some cases, stricter sanctions promulgated by other
countries, including Japan, Switzerland, Australia, the United
Kingdom, the European Union --- and this is not a comprehesive list.
For better or for worse, the Russian Federation has managed to annoy
quite a large number of countries, and many of us either live in, or
work for companies domiciled in one of them.  If you work for a
company which is a member of te Linux Foundation, Mike Dolan or some
other LF lawyer should have reached out to your General Counsel; so
talk to your legal department.)

Cheers,

						- Ted

  reply	other threads:[~2025-07-07  3:06 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 [this message]
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=20250707030609.GA13852@mit.edu \
    --to=tytso@mit.edu \
    --cc=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).