mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dylan ‎ ‎" <falaichte@mailfence.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	torvalds@linux-foundation.org
Subject: Re: Russians in the Kernel
Date: Tue, 5 Nov 2024 17:34:11 +0100 (CET)	[thread overview]
Message-ID: <1644432842.140359.1730824451296@fidget.co-bxl> (raw)
In-Reply-To: <20241105160622.GV1350452@ZenIV>

> For another,
any proxy set up to bypass the sanctions that really exist (i.e.
based on employment by sanctioned companies) would fall under the
same sanctions.

You could make the argument that sanctions as per the laws of the United States is itself unconstitutional as it impedes people's right to freedom of assembly. Even then, there is still the point that the Linux kernel and similar open source projects are transnational communities and by prohibiting access to participation you aren't respecting the spirit of free and open source software. Where anyone may participate regardless of their walk of life. I can understand not wanting to incur the wrath of the American government and that it is better to comply in some cases than make a stand as has been the case with Nintendo and emulation. I just simply don't like the amount of governmental overreach with that particular executive order and believe that it should be undermined wherever legally possible. 

Though I'll understand if the idea does end up getting anywhere. I just thought that it was worth sharing nonetheless.

> For another, you really don't want to set anything with even
the slightest whiff of "that's how to hide patch origin and/or
evade review" - that's an open invitation to any organization
that wants to feed something underhanded into the kernel.
Won't be a healthy place to hang around, to put it very mildly.

The difference is that it would all be above board with the intermediary acting as a buffer between those targeted by sanctions and the work they've done. It's all open source anyway, so there's nothing that can be done if their source code was forked and then used upstream in a patch series.

-- 
Sent with https://mailfence.com  
Secure and private email

  reply	other threads:[~2024-11-05 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1116521637.127547.1730818127738@fidget.co-bxl>
     [not found] ` <1552791356.130304.1730819601359@fidget.co-bxl>
2024-11-05 15:15   ` Dylan ‎ ‎
2024-11-05 16:06     ` Al Viro
2024-11-05 16:34       ` Dylan ‎ ‎ [this message]
2024-11-26  2:49         ` Dylan ‎ ‎

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=1644432842.140359.1730824451296@fidget.co-bxl \
    --to=falaichte@mailfence.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®