From: Yasuaki Kudo <yasu@yasuaki.com>
To: Jean Louis <bugs@gnu.support>
Cc: andrew <andrew@andrewyu.org>,
libreplanet-discuss <libreplanet-discuss@libreplanet.org>
Subject: Re: Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects
Date: Tue, 17 May 2022 17:12:36 +0900 [thread overview]
Message-ID: <617F3F2D-5974-4C3B-BCE8-C80665F0EF8E@yasuaki.com> (raw)
In-Reply-To: <YoNF4ojnnbo55e5M@protected.localdomain>
Hi Jean!
So my original question of the seemingly different attitudes toward making it clear and easy for people who want to run Free on Non-Free on (or with) software remains, and I am excited to get more clarification!
> You seem to have an opinion that community should talk about
> proprietary software even if it is exclusively not about proprietary
> software. Why do you have that urge to enforce a subject which is
> clearly not the goal of the community?
I think a little more nuanced description is in order. So there are GNU projects that do mention (talk about) proprietary systems such as Windows, make it available on them, and so on, as we have seen in responses.
Now, people from such projects that make the software available on proprietary systems - are they "enforcing a subject which is not the goal of the community?"
Might it be the case that Guix community will happily discuss how to enable the 'careless Linux' (if I may say so, instead of 'regular', for that with proprietary BLOBs), so as long as there are periodic notices, enticing them to find the Free alternatives?
-Yasu
_______________________________________________
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 13:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 2:25 Question of Aiding and Abetting Proprietary (or non-free) Software in GNU projects 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 [this message]
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
[not found] <mailman.83.1652716864.26523.libreplanet-discuss@libreplanet.org>
2022-05-16 17:49 ` 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
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=617F3F2D-5974-4C3B-BCE8-C80665F0EF8E@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=andrew@andrewyu.org \
--cc=bugs@gnu.support \
--cc=libreplanet-discuss@libreplanet.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).