From: "Gábor Boskovits" <boskovits@gmail.com>
To: myglc2@gmail.com
Cc: Guix-devel <guix-devel@gnu.org>,
guix-devel-bounces+amirouche=hypermove.net@gnu.org
Subject: Re: Roadmap for Guix 1.0
Date: Thu, 30 Aug 2018 22:12:36 +0200 [thread overview]
Message-ID: <CAE4v=pi0Qoyrc4M5wKb+UqN0KgeM81_k4RFSpCCp2ZqdK9DxgQ@mail.gmail.com> (raw)
In-Reply-To: <87a7p3zmzu.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3128 bytes --]
George Clemmer <myglc2@gmail.com> ezt írta (időpont: 2018. aug. 30., Cs,
21:14):
>
> Ricardo Wurmus <rekado@elephly.net> writes:
>
> > Ludovic Courtès <ludo@gnu.org> writes:
> >
> >> Hello,
> >>
> >> I think “Guix System” is OK.
> >
> > I think so too.
>
> I recommend against renaming GuixSD >> "Guix System". Here is Why:
>
> 1) A noob would expect "guix system" to refer to the whole Guix
> enchilada. If we use it to refer to GuixSD, a specific Guix deployment
> mode, we have created a new, counter-intuitive thing we have to explain.
>
> 2) As Ricardo points out below, the "guix system" command clashes with
> this use of Guix system. This is a second counter-intuitive thing we
> would have to explain.
>
> Bottom line: we shouln'd use the general term "Guix System" in any way
> beyond, perhaps in a descriptway way, e.g., The Guix project develops
> the Guix System, a set of tools that manage software environments.
>
> >> 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. :-)
> >
> > Exactly.
> >
> > I wrote this on IRC:
> >
> > The name “GuixSD” is opaque and creates an arbitrary distinction between
> > the system running on bare metal and the systems you can create with the
> > “guix system” commands. It makes it difficult to communicate about
> > Guix. Do we really offer “a package manager” and a “distro” — or is it
> > really all one thing with various levels?
> >
> > The “guix system” command can be used without GuixSD to create Guix
> > virtual machines or containers. Describing “guix system” is difficult
> > when we think in terms of “package manager” vs “distro”. Guix itself is
> > also a distro – none of the packages it provides link with the host
> > system, and the collection of packages is a distribution of free
> > software.
> >
> > I think that simplifying the name by using “guix” as a category will
> > make communication easier.
> >
> >> 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.
> >
> > I agree.
>
> I agree too. You may recall that I recommendi this approach when we
> discussed the web site in January. That thread includes a product
> description [1] that might be a good place to start when describing the
> "whole tool set".
>
> [1] https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00457.html
>
> What do you think about GuixSD >> "Guix Distribution"? This naming seems
to resolve the ambiguities mentioned so far, and has a widespread
use, that exactly matches the intended meaning. WDYT?
[-- Attachment #2: Type: text/html, Size: 3993 bytes --]
next prev parent reply other threads:[~2018-08-30 20:12 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 [this message]
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='CAE4v=pi0Qoyrc4M5wKb+UqN0KgeM81_k4RFSpCCp2ZqdK9DxgQ@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel-bounces+amirouche=hypermove.net@gnu.org \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
/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).