From: "Felipe López" <felipe.lopez@openmailbox.org>
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New year, new name!
Date: Tue, 06 Jan 2015 14:05:13 -0500 [thread overview]
Message-ID: <54AC31E9.3070908@openmailbox.org> (raw)
In-Reply-To: <20150106122821.4cc9d9a0@freedom-laptop>
On 06/01/15 09:28, Bruno Félix Rezende Ribeiro wrote:
> Em Mon, 05 Jan 2015 09:40:48 -0500
> Felipe López <felipe.lopez@openmailbox.org> escreveu:
>
>> I still think that calling the Guix distro "GNU" would have been
>> better, and I don't see how calling it "Guixotic - the reference
>> distribution of GNU" is any different from calling it "GNU", since
>> saying "the reference distro" implies the same issues RMS and others
>> saw in calling the distro "GNU".
>
> I agree. In fact calling it "GNU's reference distribution" could even
> worsen the problems seen by RMS, because of the explicit goal
> attributed to the distribution of being used as a canonical template.
> To me the purpose of the GNU project is more ethical and symbolic than
> technical: to provide the mythical --- entirely free --- GNU system
> and not necessarily to make a distribution for technical reference.
> IMHO, the GNU project is missing the point.
>
Yes, I think that most of the GNU people are very technical, so they
tend to think in low-level terms. This, IMHO, makes it more difficult
for the average Jane to know about GNU and its philosophy.
> Needless to say, I'll continue to call it simply "GNU". I invite
> everyone else to do the same. Given that the GNU+Linux operating
> system has gotten the wrong name "Linux" by habit and popularity,
> maybe we could make "Guixotic" (or whatever) get the right name "GNU"
> by a similar practice.
>
>
I'll do that too when I start distributing and writing about "Guixotic"
where I live.
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/
ID Klefo PGP : 0x8A296B99
Marko fingrala: 7ED8 4963 C881 647C 9DA0 FDE6 881B 91ED 8A29 6B99
next prev parent reply other threads:[~2015-01-06 18:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 15:12 New year, new name! Ludovic Courtès
2015-01-05 10:35 ` Adam Pribyl
2015-01-05 10:43 ` John Darrington
2015-01-05 14:40 ` Felipe López
2015-01-06 14:28 ` Bruno Félix Rezende Ribeiro
2015-01-06 14:58 ` Taylan Ulrich Bayırlı/Kammer
2015-01-06 19:05 ` Felipe López [this message]
2015-01-05 11:29 ` Taylan Ulrich Bayırlı/Kammer
2015-01-05 11:53 ` Svetlana Tkachenko
2015-01-05 15:30 ` Taylan Ulrich Bayırlı/Kammer
2015-01-05 16:15 ` Ludovic Courtès
2015-01-05 16:53 ` Felipe López
2015-01-05 22:11 ` Taylan Ulrich Bayırlı/Kammer
2015-01-05 22:50 ` Ludovic Courtès
2015-01-05 15:09 ` Thompson, David
2015-01-05 19:22 ` Andreas Enge
2015-01-05 19:56 ` Ludovic Courtès
2015-01-13 10:20 ` Ludovic Courtès
2015-01-22 17:30 ` New year, new name² Ludovic Courtès
2015-01-26 1:06 ` Daniel Pimentel
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=54AC31E9.3070908@openmailbox.org \
--to=felipe.lopez@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=oitofelix@gnu.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.
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).