all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: guix-devel@gnu.org
Subject: Re: Guix pronunciation
Date: Mon, 11 Mar 2019 22:06:59 +0100	[thread overview]
Message-ID: <cuc5zspnmrw.fsf@lprndn.info> (raw)
In-Reply-To: <y35mu2po.fsf@yandex.com> (mikadoZero's message of "Sun, 10 Mar 2019 12:13:55 -0400")

Hello

mikadoZero <mikadozero@yandex.com> writes:

> Doing this duckduckgo site search:  `geeks
> site:https://www.gnu.org/software/guix/` gives me only one match.  Which
> is footnote 1 of section 1 Introduction of the manual.  I do not know of
> anywhere else where the pronunciation of Guix is explicitly stated.
>
> I would like to know what other think about making the pronunciation of
> Guix obvious to anyone who visits the website.  The reasoning for this is
> because the pronunciation of Guix as "geeks" is not intuitive.  I
> think a lot of people will assume it is pronounced some other way.  For
> example "gwixs" or "gooixs".  I was not sure how to say Guix before
> watching a talk on Guix.  It is also easy for people to miss that single
> footnote in the manual on how to pronounce Guix.
>
> I think the confusion around the pronunciation of GIF would probably be
> a worst case scenario.
> https://en.wikipedia.org/wiki/Graphics_Interchange_Format#Pronunciation_of_GIF
>
> Here are two projects that have non obvious pronunciation that address
> this issue directly on their project homepage:
>
> https://asciinema.org/
> http://www.lighttpd.net/
>

I understand your concern but in my opinion, Guix doesn't really need to
enforce or be protective regarding a particular pronunciation. It's an
international and multicultural project, we all more than probably don't
have the same accent and wont't ever pronounce it the same way and I
think it's fine. :)
If someone asks for the correct way to pronounce Guix, IMHO "However you
wish" is ok and if a user needs more, the footnote in the manual can give
some "historical" insights.
I feel like it's more aligned with what Guix is. (in opposition to what
a company would do)
But, really, if the need arises, I don't mind.
Just giving my two cents.

Good evening,

Lprndn

  parent reply	other threads:[~2019-03-11 20:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 16:13 Guix pronunciation mikadoZero
2019-03-10 17:20 ` Tobias Geerinckx-Rice
2019-03-11  2:45   ` mikadoZero
2019-03-11 22:32     ` George Clemmer
2019-03-10 17:21 ` Tobias Geerinckx-Rice
2019-03-12 12:48   ` Ludovic Courtès
2019-03-12 13:05     ` Laura Lazzati
2019-03-12 13:12       ` Pierre Neidhardt
2019-03-12 13:21         ` Laura Lazzati
2019-03-13 14:10       ` Ludovic Courtès
2019-03-13 15:08         ` Laura Lazzati
2019-03-15  1:10       ` mikadoZero
2019-03-10 17:51 ` sirgazil
2019-03-11  1:43   ` mikadoZero
2019-03-11 21:26   ` Laura Lazzati
2019-03-11 21:06 ` L p R n d n [this message]
2019-03-11 23:51 ` Leo Famulari
2019-03-12  4:52 ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cuc5zspnmrw.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.