From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guix-devel@gnu.org,
Guix-devel <guix-devel-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: Roadmap for Guix 1.0
Date: Thu, 30 Aug 2018 13:46:13 +0200 [thread overview]
Message-ID: <875zzsdqm2.fsf@ambrevar.xyz> (raw)
In-Reply-To: <3950fd65549969614ebbcd16ed974f26@hypermove.net>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
> >> ** TODO “GuixSD” renamed to “Guix System”?
>
> Guix System is not good because "system" is a word that is too generic.
>
> What about "Guix OS"?
>
> >> ** TODO “Cuirass” renamed to “Guix CI”?
>
> OK
On the one hand, OS and CI are rather ubiquitous.
On the other hand, I've personally always been wary of excessive use of
abbreviations: newcomers will find documentation and communication cryptic,
while abbreviations proliferate, sometimes out of control.
But I don't think it's the case for Guix OS and even Apple went for "macOS" so I
guess "OS" is pretty safe (much more than "SD" at least).
Conversely, "Guix CI" is much less widespread, although I suppose many
developers are familiar with the term. I personally prefer unique, easy names
to abbreviations.
- The name "Guix CI" tells developers what it is (continuous integration) while
"Cuirass" does not. This is mostly true, however, for almost all applications
(mpv, firefox, chromium, emacs, <add almost everything here>).
- If we get started with Guix CI and Guix OS, I'm afraid that soon enough we
will end up with a bunch Guix FS, Guix IP, Guix CD...
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-08-30 11:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 15:18 Roadmap for Guix 1.0 Ludovic Courtès
2018-07-30 1:23 ` Pjotr Prins
2018-07-30 9:02 ` Nils Gillmann
2018-07-30 12:47 ` Pierre Neidhardt
2018-08-19 11:06 ` LVM support Ludovic Courtès
2018-08-29 16:12 ` Roadmap for Guix 1.0 Amirouche Boubekki
2018-08-30 11:46 ` Pierre Neidhardt [this message]
2018-08-30 12:04 ` Ludovic Courtès
2018-08-30 12:57 ` Ricardo Wurmus
2018-08-30 14:20 ` Tobias Geerinckx-Rice
2018-08-30 15:17 ` Nils Gillmann
2018-08-30 19:13 ` George Clemmer
2018-08-30 20:12 ` Gábor Boskovits
2018-08-31 14:25 ` George Clemmer
2018-08-31 15:45 ` Vincent Legoll
2018-08-31 15:54 ` Amirouche Boubekki
2018-09-01 7:36 ` rchar01
2018-09-01 9:27 ` Pjotr Prins
2018-09-01 10:09 ` Nils Gillmann
2018-08-30 15:36 ` George Clemmer
2018-08-30 17:11 ` Hartmut Goebel
2018-08-30 18:17 ` Jan Nieuwenhuizen
2018-08-30 21:45 ` Taylan Kammer
2018-07-30 5:08 ` Chris Marusich
2018-07-30 7:33 ` Pierre Neidhardt
2018-08-19 11:19 ` Ludovic Courtès
2018-08-19 11:11 ` Ludovic Courtès
2018-08-20 1:12 ` Chris Marusich
2018-08-30 19:34 ` Ricardo Wurmus
2018-08-19 21:52 ` Amirouche Boubekki
2018-08-20 7:44 ` Ricardo Wurmus
2018-08-29 16:05 ` Amirouche Boubekki
2018-09-04 22:55 ` fis trivial
2018-09-04 23:09 ` Adam Van Ymeren
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=875zzsdqm2.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=amirouche@hypermove.net \
--cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
--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 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).