From: Valentino Giudice <valentino.giudice96@gmail.com>
To: Aaron Wolf <wolftune@riseup.net>
Cc: Jean Louis <bugs@gnu.support>, gregor <podrzaj.gregor@gmail.com>,
Arthur Torrey <arthur_torrey@comcast.net>,
LibrePlanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: Re: Should we take steps to reduce russian access to Free Software?
Date: Tue, 1 Mar 2022 20:10:44 +0100 [thread overview]
Message-ID: <CANC0hWg-5AJgrOguqnhWGow7ZesZhHUrXAx77OicnEt-n3XV1A@mail.gmail.com> (raw)
In-Reply-To: <2f426d13-f49f-1c3f-eb02-32167e2ddabd@riseup.net>
Speaking for myself, I agree with what Aaron has written now.
I was highlighting a problem which affects many free software
organizations. There is no reason why this problem should affect free
software organizations in particular and it's in principle unrelated
to free software. It's just that I could name many free software
organizations that make political statements outside of their mission.
I would say, indeed, that being a software developer, or even the
developer of a particular piece of software being used in war, and
commenting on the actions of parties involved in such war, are two
independent things: anyone can make such comments. Such comments also
don't affect one's right to use the software, neither legally nor
morally.
Obviously, as we now agree, such statement are not the job of
mission-driven orgs (except when part of the mission).
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-03-01 19:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 17:43 Should we take steps to reduce russian access to Free Software? Arthur Torrey
2022-02-24 17:57 ` 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 [this message]
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=CANC0hWg-5AJgrOguqnhWGow7ZesZhHUrXAx77OicnEt-n3XV1A@mail.gmail.com \
--to=valentino.giudice96@gmail.com \
--cc=arthur_torrey@comcast.net \
--cc=bugs@gnu.support \
--cc=libreplanet-discuss@libreplanet.org \
--cc=podrzaj.gregor@gmail.com \
--cc=wolftune@riseup.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 read-only IMAP folder(s) and NNTP newsgroup(s).