From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Roadmap for =?utf-8?Q?Guix=C2=A01=2E0?= Date: Thu, 30 Aug 2018 14:57:46 +0200 Message-ID: <87k1o89flh.fsf@elephly.net> References: <878t5udq9u.fsf@gnu.org> <20180730012352.k56ka6psrtsofjv2@thebird.nl> <3950fd65549969614ebbcd16ed974f26@hypermove.net> <875zzsdqm2.fsf@ambrevar.xyz> <87wos8xdqm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50406) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvMWj-00041Y-9i for guix-devel@gnu.org; Thu, 30 Aug 2018 08:58:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvMWf-00043R-8k for guix-devel@gnu.org; Thu, 30 Aug 2018 08:58:21 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21081) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fvMWf-00043F-1F for guix-devel@gnu.org; Thu, 30 Aug 2018 08:58:17 -0400 In-reply-to: <87wos8xdqm.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, Guix-devel Ludovic Court=C3=A8s writes: > Hello, > > Pierre Neidhardt skribis: > >> 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 appl= ications >> (mpv, firefox, chromium, emacs, ). >> >> - If we get started with Guix CI and Guix OS, I'm afraid that soon enoug= h we >> will end up with a bunch Guix FS, Guix IP, Guix CD... > > I think =E2=80=9CGuix System=E2=80=9D is OK. I think so too. > Most of the time we=E2=80=99ll just say =E2=80=9CGuix=E2=80=9D, as > is already the case, and when we need to disambiguate (for instance when > addressing bugs), we=E2=80=99ll ask =E2=80=9CAre you using Guix System?= =E2=80=9D or =E2=80=9CAre you > using the Guix distro?=E2=80=9D, and everything will be fine. :-) Exactly. I wrote this on IRC: The name =E2=80=9CGuixSD=E2=80=9D is opaque and creates an arbitrary distin= ction between the system running on bare metal and the systems you can create with the =E2=80=9Cguix system=E2=80=9D commands. It makes it difficult to communica= te about Guix. Do we really offer =E2=80=9Ca package manager=E2=80=9D and a =E2=80= =9Cdistro=E2=80=9D =E2=80=94 or is it really all one thing with various levels? The =E2=80=9Cguix system=E2=80=9D command can be used without GuixSD to cre= ate Guix virtual machines or containers. Describing =E2=80=9Cguix system=E2=80=9D i= s difficult when we think in terms of =E2=80=9Cpackage manager=E2=80=9D vs =E2=80=9Cdis= tro=E2=80=9D. Guix itself is also a distro =E2=80=93 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 =E2=80=9Cguix=E2=80=9D as a cate= gory will make communication easier. > The motivation for this name change is that =E2=80=9CSD=E2=80=9D is obscu= re to most, as > you note, plus it creates confusion when people visit the web site: the > web site has a =E2=80=9CGuixSD=E2=80=9D logo, but then it talks about fea= tures of the > package manager. Designating the whole tool set as =E2=80=9CGuix=E2=80= =9D will simplify > this, and we can always be more specific when we need to. I agree. -- Ricardo