unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: 25254@debbugs.gnu.org
Subject: bug#25254: [minor] 'About' page says GuixSD is a "GNU/Linux distribution"
Date: Sun, 25 Dec 2016 12:39:36 +0100	[thread overview]
Message-ID: <87pokgnsp3.fsf@elephly.net> (raw)
In-Reply-To: <87r34ywqat.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]


Taylan UlrichBayırlı/Kammer <taylanbayirli@gmail.com> writes:

> It would be better to be consistent with the home page and make clear
> that GuixSD is a GNU distribution, with Linux-libre being the default
> kernel for the foreseeable future.
>
> Background: Wikipedia has a policy to call GNU/Linux distributions
> "Linux distribution" because that wrong term is more commonly used by
> the public.  To define GuixSD as a "GNU/Linux distribution" gives them
> in turn justification to define it as a "Linux distribution" instead.

FWIW, I like to call the system just “GNU” and GuixSD a “variant of the
GNU system”.  To me “Linux” is a technical detail that doesn’t need to
be mentioned explicitly each time when speaking to a general audience.
(This can be extended to “variant of the GNU system with Linux” when
needed, or just “GNU with Linux”, which is really close to “GNU+Linux”
or the more ambiguous “GNU/Linux”.)

The name affirms the vision towards which we’re working, and it
acknowledges the concerted effort in getting us so far.  The name is not
about acknowledging *software* as such.

I feel that convincing the current set of Wikipedia editors is a lost
cause.  It looks even worse in the German Wikipedia, where the “article”
on the GNU/Linux naming controversy insinuates that this is primarily
about stroking the egos of rms and the small group of GNU developers.
(I just spent some time submitting some changes to that page.)

I’d be okay with another way to describe what GuixSD is (especially once
we offer an additional image using the Hurd), but I’m also fine with
leaving it as it is.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
http://elephly.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

  parent reply	other threads:[~2016-12-25 11:40 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 [this message]
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
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=87pokgnsp3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=25254@debbugs.gnu.org \
    --cc=taylanbayirli@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.
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).