From: Jean Louis <bugs@gnu.support>
To: Aaron Wolf <wolftune@riseup.net>
Cc: Valentino Giudice <valentino.giudice96@gmail.com>,
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: Wed, 2 Mar 2022 11:02:09 +0300 [thread overview]
Message-ID: <Yh8kgcVqm/U2LwBf@protected.localdomain> (raw)
In-Reply-To: <2f426d13-f49f-1c3f-eb02-32167e2ddabd@riseup.net>
* Aaron Wolf <wolftune@riseup.net> [2022-03-01 19:21]:
> 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
I allow Devin to speak for himself, as he did not declare to have you
being authorized to speak on his behalf.
I wish organizations in general would have better understanding of
corporate duties and obligations and powers issues to its officers.
And I don't blame Devin for such mistakes. But awareness should be
there that mistakes may impact community.
That is why in every serious organization one has to know how to speak
in public. As I do not represent any serious organization, I allow
myself little bit more freedom, but when I do, then I speak seriously
and aligned to my organization's goals and purposes, acts, laws,
orders, etc. I don't just speak out of my personal feelings.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-03-02 15:32 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
2022-03-02 8:02 ` Jean Louis [this message]
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=Yh8kgcVqm/U2LwBf@protected.localdomain \
--to=bugs@gnu.support \
--cc=arthur_torrey@comcast.net \
--cc=libreplanet-discuss@libreplanet.org \
--cc=podrzaj.gregor@gmail.com \
--cc=valentino.giudice96@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).