From: Jean Louis <bugs@gnu.support>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: lkcl <luke.leighton@gmail.com>,
"Discussão do LibrePlanet" <libreplanet-discuss@libreplanet.org>,
libreplanet-discuss-request@libreplanet.org
Subject: Re: Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects
Date: Tue, 17 May 2022 16:48:36 +0300 [thread overview]
Message-ID: <YoOntDOtw8SRz2T3@protected.localdomain> (raw)
In-Reply-To: <4EA2BCAD-9C73-47AA-927E-EFC4B47948B2@yasuaki.com>
* Yasuaki Kudo <yasu@yasuaki.com> [2022-05-17 16:32]:
> Hi,
>
> I just wanted to follow up that I meant to ask:
>
> - Endorsing Free Software to be available on non-free systems, so as
> - long as it is understood that it is an invitation to the fully
> - Free System, not just partial - is this stance well shared among
> - the members and participants of FSF/GNU projects? Or is it the
> - case that Richard Stallman is rather uniquely more generous than
> - others?
When free software is created it normally does fit into various
standards and various operating systems, and free software may run on
many versions of Windows, UNIX, and UNIX-licensed proprietary systems,
not only on FreeBSD and BSD versions of UNIX, not only on Linux based
systems, and so on.
Users are supported in running free software no matter what underlying
operating system is.
If software runs exclusively on proprietary system, then such IMHO is
not endorsed by GNU Project. You got it right.
Maybe you should find appropriate mailing list on GNU project, as
Libreplanet is FSF's mailing list:
GNU Mailing Lists
https://lists.gnu.org/mailman/listinfo/
Maybe GNU Misc Discuss is for that question more appropriate.
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-05-17 14:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.83.1652716864.26523.libreplanet-discuss@libreplanet.org>
2022-05-16 17:49 ` Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects lkcl
2022-05-17 0:59 ` Yasuaki Kudo
2022-05-17 9:53 ` lkcl
2022-05-17 10:38 ` Yasuaki Kudo
2022-05-17 12:05 ` lkcl
2022-05-17 12:51 ` Yasuaki Kudo
2022-05-17 13:48 ` lkcl
2022-05-17 14:17 ` Yasuaki Kudo
2022-05-17 14:40 ` Greg Farough
2022-05-17 15:38 ` Andrew Yu via libreplanet-discuss
2022-05-18 0:55 ` Yasuaki Kudo
2022-05-17 17:14 ` Jean Louis
2022-05-17 13:48 ` Jean Louis [this message]
2022-05-15 2:25 Yasuaki Kudo
2022-05-15 17:11 ` andrew via libreplanet-discuss
2022-05-16 9:10 ` Yasuaki Kudo
2022-05-16 11:08 ` andrew via libreplanet-discuss
2022-05-16 11:55 ` Yasuaki Kudo
2022-05-17 6:51 ` Jean Louis
2022-05-17 6:57 ` andrew via libreplanet-discuss
2022-05-17 8:12 ` Yasuaki Kudo
2022-05-17 8:48 ` andrew via libreplanet-discuss
2022-05-17 13:35 ` Jean Louis
2022-05-17 14:02 ` Yasuaki Kudo
2022-05-18 3:12 ` Alexandre Oliva
2022-05-17 6:39 ` Jean Louis
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=YoOntDOtw8SRz2T3@protected.localdomain \
--to=bugs@gnu.support \
--cc=libreplanet-discuss-request@libreplanet.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=luke.leighton@gmail.com \
--cc=yasu@yasuaki.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).