unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
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 11:36:29 -0400	[thread overview]
Message-ID: <87bm9jzx1e.fsf@gmail.com> (raw)
In-Reply-To: <87wos8xdqm.fsf@gnu.org>

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> Hello,
>
> Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>
>> - 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...
>
> I think “Guix System” is OK.  Most of the time we’ll just say “Guix”, as
> is already the case, and when we need to disambiguate (for instance when
> addressing bugs), we’ll ask “Are you using Guix System?” or “Are you
> using the Guix distro?”, and everything will be fine.  :-)
>
> The motivation for this name change is that “SD” is obscure to most, as
> you note, plus it creates confusion when people visit the web site: the
> web site has a “GuixSD” logo, but then it talks about features of the
> package manager.  Designating the whole tool set as “Guix” will simplify
> this, and we can always be more specific when we need to.

This is good because it declutters the Guix-Verse for new users.

I suggest that the distinction between GuixOS, package manager, QEMU
image, and source can be re-positioned as download options.

We could simplify the choice of these by improving the download
page. For example ...

1) We could simplify the download labels/descriptions, e.g.,

   "GuixSD 0.15.0 QEMU Image QCOW2 virtual machine (VM) image. Download
   options: x86_64"

   ... might become ...

   "x86_64 VM (GuixSD 0.15.0 QEMU Image QCOW2 virtual machine image)"

2) We could add a feature check list that helps with download selection.

With such changes the support question is: what did you download?

IMO it would be desirable to pick a single term for each download option
and use it obsessively throughout the site and doc. This small thing can
be quite helpful to a noob because it eliminates any confusion that
might be caused by multiple terms meaning the same thing. So, IMO we
should settle on only one of Guix System, GuixSD, GuixOS, or maybe "Guix
bare metal".

- George

  parent reply	other threads:[~2018-08-30 15:49 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
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 [this message]
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=87bm9jzx1e.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).