From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia@riseup.net Subject: Re: Communication and Design at Guix Date: Wed, 16 Jan 2019 16:10:51 -0800 Message-ID: References: <87k1jfuk26.fsf@gnu.org> <875zus1b2t.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 ([209.51.188.92]:52772) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gjvGr-00056L-BT for guix-devel@gnu.org; Wed, 16 Jan 2019 19:10:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gjvGq-0002Ps-6Q for guix-devel@gnu.org; Wed, 16 Jan 2019 19:10:57 -0500 In-Reply-To: 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: George Clemmer Cc: guix-devel@gnu.org, Guix-devel , L p R n d n On 2019-01-16 16:31, George Clemmer wrote: > Hi Lprndn, >=20 > I am glad to see your interest in these issues. >=20 > Ludovic Court=C3=A8s writes: >=20 >> Hi, >> >> L p R n d n skribis: >> >>> Ludovic Court=C3=A8s writes: >> >> [...] >> >>>> A very concrete task that could be of interest to you is the =E2=80=9C= name >>>> change=E2=80=9D (a bit of a strong word) that we=E2=80=99d like to i= mplement by 1.0. >>>> I=E2=80=99ll try to summarize. Currently we have =E2=80=9CGuix=E2=80= =9D and =E2=80=9CGuixSD=E2=80=9D, and that >>>> confuses things: people visit the web site, they see a =E2=80=9CGuix= SD=E2=80=9D logo and >>>> get confused because they were just looking for a package manager, n= ot a >>>> whole distro, or they think =E2=80=9CGuixSD=E2=80=9D is a storage de= vice ;-), things >>>> like that. >>>> >>>> The idea is to bring everything under the =E2=80=9CGuix=E2=80=9D nam= e. Most of the >>>> time, writing =E2=80=9CGuix=E2=80=9D is good enough=E2=80=94after al= l, one can run =E2=80=98guix system=E2=80=99 >>>> on a foreign distro, too. When we really need to make the distincti= on, >>>> for instance in the manual, we would write =E2=80=9CGuix System=E2=80= =9D to designate >>>> what we currently call =E2=80=9CGuixSD=E2=80=9D. >>> >>> Hum. It might just be as easy as getting rid of the GuixSD logo and >>> wording for the most part. Then we can find a *preferred* way to >>> designate GuixSD (a Guix system (probably), Guix distro, Guix os).Her= e, >>> it's more about making GuixSD "disappear" but we could also just rebr= and >>> GuixSD with some kind of "subtitle": "Guix, the system", derive a log= o >>> from the Guix's one. It depends a lot from what we want to put under >>> the spotlight. >> >> The idea is more to have a single =E2=80=9Cbrand=E2=80=9D: Guix. >=20 > Yes a single brand is the way to go. But, piecemeal changes to the web > site are unlikely to get us there unless we work from a unified "Guix > Brand" product description. E.g., earlier I proposed ... >=20 > "'Guix' is a software environment manager that creates user environment= s > that are completely and independently specified by users. Guix users ar= e > never stuck needing software that a Sysadmin can't, won't, or hasn't > installed. A Guix user can run multiple, differing environments > simultaneously and can replicate any environment on any Guix run-time > platform. Guix provides system-wide environment management when > appropriate to the run-time platform. Creation, modification, and > upgrade are atomic and roll-back is instantaneous, so Guix users and > sysadmins are never stuck with a broken user environment or system. > Guix implements a functional specification of package, user, and system > configurations using the Scheme language. Guix complies with the FSF > Four Essential Freedoms and Free System Distribution Guidelines and > provides easy and immediate access to the exact source being run. By > default, Guix uses pre-built package substitutes from the Guix build > farm and mirrors but users may build any package, or a complete system, > from package developer sources."[1] >=20 >> Then =E2=80=9CGuix System=E2=80=9D would be a component of Guix, so to= speak, similar >> to GNOME and its applications. >=20 > "Guix System" is a "bad" name for "GuixSD." Why? Because a new user's > first expectation is for "Guix system" to refer to the whole of Guix, > which we want to call "Guix" (referred to as "Guix Brand" below). >=20 > But if we call GuixSD the "Guix System", we create a counter-intuitive > thing to explain. E.g., we will be saying, "Our GNU/Linux System > Distribution, 'Guix System' is just one of multiple ways to use 'Guix > Brand', which includes the Guix package manager, for which we also use > the 'Guix Brand' label. >=20 > Another "bad" thing about calling it "Guix system" is that when a user > searches "guix system" they hit the 'guix system' "Guix Brand" package > manager' command that, BTW, also generates "Guix VMs". >=20 > It will simplify our work if we present GuixSD as simply one of several > Guix download/deployment options. E.g., earlier I suggested ... >=20 > "Guix is available on multiple run-time platforms including bare metal > (GuixSD), Virtual Machines (QEMU image), and any GNU/Linux distro (Guix > Binary).[1]" >=20 > With this approach, we only need a distinctive label for GuixSD that > doesn't puzzle users to produce reliable search hits on the relevant > parts of our message and documentation. E.g., GuixOS. >=20 > HTH - George >=20 > [1] https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00444.html +1 Nice work George.=20 GuixOS gives us the advantage of OS already being known as a complete useful separate thing to boot and install (e.g. NixOS, ReactOS, Chrome OS, iOS, etc.) Guix is now an octopus with many arms :) --=20 Cheers=20 Swedebugia