all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org, "Pierre Neidhardt" <mail@ambrevar.xyz>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth.
Date: Wed, 27 Mar 2019 14:20:20 +0100	[thread overview]
Message-ID: <BCA582AA-25D0-4375-A608-EC533D6D5D72@riseup.net> (raw)
In-Reply-To: <87r2aso7zh.fsf@ambrevar.xyz>

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

Pierre Neidhardt <mail@ambrevar.xyz> skrev: (27 mars 2019 12:46:26 CET)
>Ludovic Courtès <ludo@gnu.org> writes:
>
>> Apologies if I missed a previous discussion on this topic, but… I’m
>> skeptical about the renames.  I assume that the original names were
>> those commonly used in distributions, which in itself may be a good
>> reason to keep them.
>
>Names may vary a lot across distributions.  Especially when it comes to
>games, since they tend to have more exotic titles.
>
>If the majority of distributions decides on a poor name, we don't have
>to repeat the same mistake ;)
>
>> Those names are also used upstream in some cases: the tarball for
>> wesnoth is called “westnoth*.tar.gz”, for example, and the GitHub
>> project of L’Abbaye des morts is “abbayedesmorts” (no ‘l’).  Like our
>> naming guidelines say (info "(guix) Package Naming"), we should try
>to
>> stick to the upstream name.
>>
>> Thoughts?
>
>I think it's important to ask "why should we name a package this way."
>What's the rationale behind a package name?
>
>We are facing the users, not package maintainers.  Users are not
>supposed to know about:
>
>- domain names
>- tarball names
>- github names
>
>Those are details, in my understanding, reserved to developers and
>packagers.
>More often than not, those shortened names are used because of
>technical
>limitations (e.g. character length).  We don't have to forward those
>limitations on ourselves.
>
>I think it makes sense that we expose to the users names that speaks to
>them, i.e. the "official project full name".
>
>Finally, as I mentioned above with the completion systems that we have,
>we've got nothing to lose in having long names.
>
>My two cents :)
>
>-- 
>Pierre Neidhardt
>https://ambrevar.xyz/

I agree with Pierre. 😃

Good useability is important and cryptic acronyms are not something to expose to the user if possible to avoid IMO. 

Maybe this is where we need to discuss what our target audience is? Nerds only?
Random Joe who is new to GNU systems but dead tired of the proprietary systems he was taught in school who heard og Guix through a good friend who helps him getting started? 

Tangent to this is the focus on an  installer. Why bother with an installer if we only target nerds and educated computer professionals?

Anyone else who have opinions on the matter of acronyms in names where they can be avoided?

-- 
Sent from my k-9 mail for Android.

[-- Attachment #2: Type: text/html, Size: 3028 bytes --]

  reply	other threads:[~2019-03-27 13:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190326131842.7363.84034@vcs0.savannah.gnu.org>
     [not found] ` <20190326131845.1B177209E3@vcs0.savannah.gnu.org>
2019-03-26 14:54   ` 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server Tobias Geerinckx-Rice
2019-03-26 14:20     ` Pierre Neidhardt
2019-03-26 15:18     ` Ricardo Wurmus
2019-03-26 15:32       ` Pierre Neidhardt
2019-03-26 17:53         ` Andreas Enge
2019-03-26 18:25           ` Pierre Neidhardt
2019-03-27 11:11           ` Ludovic Courtès
2019-03-27 11:36             ` Pierre Neidhardt
     [not found] ` <20190326131844.C73EC209E3@vcs0.savannah.gnu.org>
2019-03-27 11:07   ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth Ludovic Courtès
2019-03-27 11:46     ` Pierre Neidhardt
2019-03-27 13:20       ` swedebugia [this message]
2019-03-27 15:00         ` Ricardo Wurmus
2019-03-27 16:42           ` Pierre Neidhardt
2019-03-28  7:59             ` Ricardo Wurmus
2019-03-28  8:09               ` Pierre Neidhardt
2019-03-29 13:27           ` swedebugia
2019-03-27 15:15         ` Ludovic Courtès
2019-03-27 18:34         ` Tobias Geerinckx-Rice
2019-03-27 18:26           ` Pierre Neidhardt
2019-03-27 18:44             ` Daniel Jiang
2019-03-27 21:15             ` Tobias Geerinckx-Rice
2019-03-28  8:17               ` Pierre Neidhardt
2019-03-29 14:02                 ` Tobias Geerinckx-Rice
2019-03-29 15:16                   ` Andreas Enge
2019-03-29 16:42                     ` Naming, hacking, and policies Ludovic Courtès
2019-03-29 19:23                       ` Ricardo Wurmus
2019-03-31 16:33                         ` Ludovic Courtès
2019-03-30 13:54                       ` sirgazil
2019-03-31 16:37                         ` Ludovic Courtès
2019-03-31 18:03                           ` sirgazil
2019-03-31 20:31                             ` Ludovic Courtès
2019-03-31 22:59                               ` sirgazil
2019-04-01  0:07                               ` Tobias Geerinckx-Rice
2019-03-29 19:57                     ` 05/15: gnu: wesnoth: Rename package to the-battle-for-wesnoth swedebugia
2019-03-27 15:13       ` Ludovic Courtès
2019-03-27 16:25         ` Pierre Neidhardt

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=BCA582AA-25D0-4375-A608-EC533D6D5D72@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.