From: David Craven <david@craven.ch>
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: 25254@debbugs.gnu.org
Subject: bug#25254: [minor] 'About' page says GuixSD is a "GNU/Linux
Date: Sun, 25 Dec 2016 19:26:00 +0100 [thread overview]
Message-ID: <CAL1_immqdWH7bHmt9cqR0YnetYz64EXaYKq1jqM4j86ZqaQ1Tg@mail.gmail.com> (raw)
In-Reply-To: <86dda095c910a87e098687f346b9ed1b@openmailbox.org>
> To David, the Guix developers had the intention to call the system just GNU,
> and distribute it as GNU (Guix is a GNU project after all), but RMS didn't
> agree, so it was decided to use the GuixSD name and call it "A distribution
> of GNU", and not "THE distribution of GNU." [1]
First I appreciate all the work done by members of GNU project or any
other free software project.
I don't object to calling guixsd THE GNU operating system, because
that means that guixsd is an operating system called GNU and is a
project from the GNU organization. If we call it A GNU operating
system then it requires additional explanation. We can not expect
people to know what the criteria is for an operating system being A
GNU operating system. I've spent a considerable amount of the last 8
years learning about computers and I don't find it clear (as I
mentioned in an earlier email there are multiple possible
interpretations of what a GNU system is). If it is explained somewhere
then it is not a problem.
I also think that supporting Hurd also as a kernel does not make
guixsd not a Linux distribution, but makes guixsd both a Linux and a
Hurd distribution. I find it sensible to empathize the "better known"
one, but I don't have any attachment to a particular name or kernel.
What to call something is ultimately a marketing issue and not a
technical issue.
If I had to sell red bananas, I'd call the product a banana. Saying it
is not a banana it is a red banana, and that the main thing about the
banana is the fact that it's red so I'll market my product as simply
red isn't a sound decision in my opinion. If I ask someone do you want
to buy a banana they might say mmh yes I'm hungry, I'd like a banana
thanks. Oh cool it's a red banana! On the other hand if I go and say
do you want to buy some red? I'd expect to get a less positive
response. No thank you I don't need red.
next prev parent reply other threads:[~2016-12-25 18:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 16:42 bug#25254: [minor] 'About' page says GuixSD is a "GNU/Linux distribution" Taylan Ulrich Bayırlı/Kammer
2016-12-23 17:35 ` David Craven
2016-12-23 18:51 ` Taylan Ulrich Bayırlı/Kammer
2016-12-23 19:36 ` David Craven
2016-12-23 20:55 ` Taylan Ulrich Bayırlı/Kammer
2016-12-23 21:28 ` David Craven
2016-12-23 21:32 ` Leo Famulari
2016-12-24 11:06 ` Taylan Ulrich Bayırlı/Kammer
2016-12-24 19:49 ` Mike Gerwitz
2016-12-24 21:24 ` Taylan Ulrich Bayırlı/Kammer
2016-12-24 23:51 ` David Craven
2016-12-25 0:50 ` David Craven
2016-12-25 19:35 ` Taylan Ulrich Bayırlı/Kammer
2016-12-25 19:55 ` Leo Famulari
2016-12-25 11:39 ` Ricardo Wurmus
2016-12-25 16:45 ` bug#25254: [minor] 'About' page says GuixSD is a "GNU/Linux Luis Felipe López Acevedo
2016-12-25 18:26 ` David Craven [this message]
2016-12-25 19:50 ` Taylan Ulrich Bayırlı/Kammer
2016-12-29 22:10 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1_immqdWH7bHmt9cqR0YnetYz64EXaYKq1jqM4j86ZqaQ1Tg@mail.gmail.com \
--to=david@craven.ch \
--cc=25254@debbugs.gnu.org \
--cc=felipe.lopez@openmailbox.org \
--cc=rekado@elephly.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).