From: Matt Ivie <m0dese7en@mykolab.com>
To: Jacob Hrbek <kreyren@rixotstudio.cz>,
libreplanet-discuss@libreplanet.org
Subject: Re: Should distros take steps to reduce russian access to Free Software?
Date: Fri, 11 Mar 2022 08:16:36 -0800 [thread overview]
Message-ID: <772fc81af20eff3c545ab921dc2325b1c45d4fba.camel@mykolab.com> (raw)
In-Reply-To: <0811f5f2-f50a-6c52-8c21-04344b84beb3@rixotstudio.cz>
On Thu, 2022-03-10 at 16:01 +0000, Jacob Hrbek wrote:
>
> It's just fucking crazy to argue that us writting a software for the
> russian army is somehow a "good thing for freedom" when all rules of
> freedom are being shelled with cluster bombs in ukraine at the time
> when
> even the definition of neutrality (SWITZERLAND!!) joined up on the
> sanctions.
>
Nobody wrote the software FOR the Russian army specifically. I'm not
sure what you want everyone to do here. Do you have any army to back
your idea of restricting the Russian army from using Free Software?
Even if we suddenly changed licensing terms to exclude acts of war or
whatever that would only be active going forward, not retroactive if
I'm understanding the licenses properly. Meaning there are repositories
of software out there that would be available for use.
Also, if someone is committing a war crime, do you think they'll stop
at violating a software license? Like leveling a city was okay to them
but violating software terms is the hard line they just won't cross?
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-03-11 16:17 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 8:04 Should we take steps to reduce russian access to Free Software? 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-26 1:34 ` Should we take steps to reduce Russian access to Free Software? No J.B. Nicholson
2022-02-27 4:10 ` Should we take steps to reduce russian access to Free Software? 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 10:50 ` Should we take steps to reduce russian access to Free Software?> the headache of it all dissolves in forgiveness gregor
2022-03-02 6:18 ` Valentino Giudice
2022-03-02 6:58 ` gregor
2022-03-03 5:07 ` Richard Stallman
2022-03-03 13:51 ` gregor
2022-03-03 15:56 ` Devin Ulibarri
2022-03-03 18:45 ` Ole Aamot
2022-03-04 15:13 ` Jean Louis
2022-03-04 15:42 ` Lori Nagel via libreplanet-discuss
[not found] ` <c54b6cbc-a88a-3abf-2f60-b0fb2ca0d066@rixotstudio.cz>
2022-03-06 5:13 ` Richard Stallman
2022-03-08 11:01 ` Jacob Hrbek
2022-03-08 22:50 ` Valentino Giudice
2022-03-09 16:20 ` Should distros take steps to reduce russian access to Free Software? Félicien Pillot
2022-03-09 16:43 ` Valentino Giudice
2022-03-09 18:03 ` Erica Frank
2022-03-10 16:01 ` Jacob Hrbek
2022-03-11 16:16 ` Matt Ivie [this message]
2022-03-12 5:27 ` Jean Louis
2022-03-12 17:48 ` Aaron Wolf
2022-03-12 18:53 ` Jean Louis
2022-03-13 3:52 ` Aaron Wolf
2022-03-13 9:51 ` Federico Leva (Nemo)
2022-03-13 15:07 ` Aaron Wolf
2022-03-13 17:33 ` gregor
2022-03-13 18:51 ` Miles Fidelman
2022-03-13 20:25 ` Aaron Wolf
2022-03-12 19:36 ` Miles Fidelman
2022-03-12 23:44 ` Getting the truth into Russia Akira Urushibata
2022-03-13 17:57 ` Should distros take steps to reduce russian access to Free Software? Jean Louis
2022-03-13 23:49 ` Ron Nazarov via libreplanet-discuss
2022-03-14 1:57 ` Akira Urushibata
2022-03-14 2:01 ` Valentino Giudice
2022-03-14 5:50 ` "Open Source" is vague term referring to guns, wine, spirituality, etc Jean Louis
2022-03-14 21:01 ` Aaron Wolf
2022-03-14 21:17 ` Jean Louis
2022-03-14 21:48 ` Aaron Wolf
2022-03-15 5:26 ` Jean Louis
2022-03-14 22:01 ` Valentino Giudice
2022-03-15 6:10 ` Jean Louis
2022-03-15 11:54 ` Jean Louis
2022-03-18 6:14 ` Valentino Giudice
2022-03-11 5:15 ` Should distros take steps to reduce russian access to Free Software? Richard Stallman
2022-03-11 14:36 ` knowledgeofnations
2022-03-11 15:03 ` Miles Fidelman
2022-03-11 18:22 ` Jean Louis
2022-03-12 16:55 ` Miles Fidelman
2022-03-08 23:22 ` Should we take steps to reduce russian access to Free Software?> the headache of it all dissolves in forgiveness Matt Ivie
2022-03-09 4:21 ` Richard Stallman
2022-03-30 22:44 ` Ole Aamot
[not found] ` <CAA+nH92ffd9PqZ0S=6tvJN4K+j64J4CU8AKwSPu=McWr=eZwww@mail.gmail.com>
2022-03-31 6:32 ` Ole Aamot
2022-04-01 4:11 ` Richard Stallman
2022-03-09 8:05 ` Free software is not perpetrator Jean Louis
2022-03-09 15:21 ` Should we take steps to reduce russian access to Free Software?> the headache of it all dissolves in forgiveness Federico Leva (Nemo)
2022-03-02 11:12 ` Jean Louis
2022-03-03 5:07 ` Richard Stallman
2022-03-01 17:53 ` Should we take steps to reduce russian access to Free Software? 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=772fc81af20eff3c545ab921dc2325b1c45d4fba.camel@mykolab.com \
--to=m0dese7en@mykolab.com \
--cc=kreyren@rixotstudio.cz \
--cc=libreplanet-discuss@libreplanet.org \
--cc=m0dese7en@member.fsf.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).