From: Aaron Wolf <wolftune@riseup.net>
To: Jean Louis <bugs@gnu.support>,
Valentino Giudice <valentino.giudice96@gmail.com>,
gregor <podrzaj.gregor@gmail.com>
Cc: 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 08:20:33 -0800 [thread overview]
Message-ID: <2f426d13-f49f-1c3f-eb02-32167e2ddabd@riseup.net> (raw)
In-Reply-To: <13F4411F-83E8-498C-A5AF-1E468C289971@gnu.support>
There has been a lot of overreacting to a minor post here.
I will readily agree that I was simply wrong when *I* (personally, I
represent no organization here) suggested that the FSF could make a
statement about war. There's a degree to which the org can say some
things, but indeed it is a mission-driven organization that should not
take sides in unrelated political debates.
That said, Devin didn't take sides in any sense or say anything
inappropriate on behalf of the FSF. The only intention of his message
was to say essentially, "FSF will comply with any legal requirements
imposed on it" without even suggesting that any legal requirements are
applicable at this time. The idea that Devin's message meant anything
other thing this is pure misunderstanding.
The gist of my original personal message was simply to assert the main
idea which I still believe: that free software organizations and
developers can state opinions independently of legal and licensing
terms. In other words, while I was clarifying that software freedoms do
not and shall not discriminate among uses and users, that does not in
itself block anyone from expressing requests and opinions about uses and
users.
In other words, I can very well say that I don't like a particular use
or user of some software without that taking away the freedoms of that
user. Similarly, FSF could potentially say that a particular corporation
is overall acting in opposition to software freedom and that FSF takes
the position of asking that corporation to forgo all use of free
software. I'm not saying FSF *should* make such a statement. I'm just
saying that FSF *may* make such a statement without it having any effect
on the actual freedoms of that corporation to use free software.
In short: political opinions are independent of software freedoms.
Political opinions may be expressed appropriately (which is typically
*inappropriate* for FSF if the opinion is unrelated to the mission). And
Devin didn't even express any opinion about anything. He only expressed
that FSF is paying attention to sanctions in order to determine whether
any legal restrictions affect FSF, and if so, FSF will comply will the law.
Aaron
On 2022-02-28 22:09, Jean Louis wrote:
> I have asked on this list the FSF representative to list references of sanctions that apply to FSF. None so far has been shown.
>
> So which sanction exactly is relevant to FSF? That they are not allowed to give Putin the membership card?
>
>
>
> On March 1, 2022 4:37:37 AM UTC, Valentino Giudice <valentino.giudice96@gmail.com> wrote:
>>> makes me sad, seeing how FSF rushes to be "politically correct" in
>> the
>>> world run by propaganda machines.
>>
>> "Politically correct" for doing what, exactly? Literally complying
>> with sanctions?
>> Don't they legally have to do that?
>>
>> _______________________________________________
>> libreplanet-discuss mailing list
>> libreplanet-discuss@libreplanet.org
>> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
>
>
> Jean
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
_______________________________________________
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 16:21 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 [this message]
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=2f426d13-f49f-1c3f-eb02-32167e2ddabd@riseup.net \
--to=wolftune@riseup.net \
--cc=arthur_torrey@comcast.net \
--cc=bugs@gnu.support \
--cc=libreplanet-discuss@libreplanet.org \
--cc=podrzaj.gregor@gmail.com \
--cc=valentino.giudice96@gmail.com \
/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).