From: Arthur Torrey <arthur_torrey@comcast.net>
To: libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: re: Should we take steps to reduce russian access to Free Software?
Date: Thu, 24 Feb 2022 12:43:59 -0500 (EST) [thread overview]
Message-ID: <333679145.1046174.1645724639817@connect.xfinity.com> (raw)
Much as we might want to shut off the Russians, I don't think this is something that the GPL type licenses allow... This has come up time and time again in regards to limiting access to all sorts of other undesirables, and the bottom line is that as long as they are complying w/ the licenses (i.e. copylefting changes, etc.) they can't be cut off...
An ironic / amusing question I remember being raised a while back: Is the question about if Free Software is used in a 'smart' weapon, (smart bomb guidance system, drone, etc.); and an intact device falls into the hands of the enemy, does that count as 'distribution' and entitle the enemy to demand the corresponding source code?
ART
================
Date: Thu, 24 Feb 2022 08:04:30 +0000
From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: Leah Rowe via libreplanet-discuss
<libreplanet-discuss@libreplanet.org>
Subject: Should we take steps to reduce russian access to Free
Software?
Message-ID: <25b59d57-597d-4ef4-9e93-2c067a1d81fc@rixotstudio.cz>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Today russian forces invaded ukraine and started an unprovoked war with
free software being used across russia and in the government thus
playing a major role in russia's war capabilities.
Should we and can we take steps to prevent/reduce russia's access to our
software?
------------------
Arthur Torrey - <arthur_torrey@comcast.net>
-------------------
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next reply other threads:[~2022-02-24 17:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 17:43 Arthur Torrey [this message]
2022-02-24 17:57 ` Should we take steps to reduce russian access to Free Software? gregor
2022-02-24 18:17 ` Arthur Torrey
2022-02-24 18:35 ` Paul Sutton via libreplanet-discuss
2022-03-01 4:37 ` Valentino Giudice
2022-03-01 6:09 ` Jean Louis
2022-03-01 16:20 ` Aaron Wolf
2022-03-01 19:10 ` Valentino Giudice
2022-03-02 8:02 ` Jean Louis
2022-02-24 18:06 ` rapt--- via libreplanet-discuss
-- strict thread matches above, loose matches on Subject: below --
2022-02-24 8:04 Jacob Hrbek
2022-02-24 17:00 ` Devin Ulibarri
[not found] ` <Yhh7tevsz3Ha5xY+@protected.localdomain>
2022-02-25 12:15 ` Devin Ulibarri
2022-02-25 15:32 ` Aaron Wolf
2022-02-26 0:48 ` Thomas Lord
2022-02-27 4:10 ` Richard Stallman
2022-03-01 4:59 ` Valentino Giudice
2022-03-01 7:52 ` Jean Louis
2022-02-27 4:11 ` Richard Stallman
[not found] ` <35700904-028a-1dbf-3d48-0478701ae0f8@gmail.com>
2022-03-01 4:24 ` Richard Stallman
2022-03-01 17:53 ` Julian Daich
2022-02-24 17:10 ` Paul Sutton via libreplanet-discuss
2022-02-24 18:03 ` Aaron Wolf
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=333679145.1046174.1645724639817@connect.xfinity.com \
--to=arthur_torrey@comcast.net \
--cc=libreplanet-discuss@libreplanet.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).