From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Communication and Design at Guix Date: Tue, 08 Jan 2019 18:37:53 +0100 Message-ID: <87k1jfuk26.fsf@gnu.org> References: 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]:50734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ggvKC-00079c-Ud for guix-devel@gnu.org; Tue, 08 Jan 2019 12:38:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ggvKA-00084z-Qc for guix-devel@gnu.org; Tue, 08 Jan 2019 12:38:00 -0500 Received: from hera.aquilenet.fr ([185.233.100.1]:47820) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ggvKA-0007v3-FR for guix-devel@gnu.org; Tue, 08 Jan 2019 12:37:58 -0500 In-Reply-To: (L. p. R. n. d. n.'s message of "Tue, 08 Jan 2019 17:49:57 +0100") 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: L p R n d n Cc: guix-devel@gnu.org Hello, L p R n d n skribis: > After taking some time learning Guix and trying to get some new packages > in, I wanted get involved in a slightly different way. I'm not good at > programming and I think my time might be better used participating in > tasks a little more inline with my skills. > The thing is that I find "design" and "communication" (take it in a very = broad > way) often a little more complex and delicate to tackle in a group > project. This is why I'm introducing the idea with this mail. This is one of the non-programming activities where Guix needs help so I=E2=80=99m glad you=E2=80=99re offering to contribute! > I think the Guix project could benefit a lot from dealing with the > "rest of the world" and how it wants to show itself. It might even help > clarify some technical decisions if needed. Bonus is that next release > will probably be 1.0 and that it means Guix will get extra attention. > > I have a few things I would like to talk about but, as I don't want to > force aniything on anyone, I wanted to first have your thoughts about thi= s and > eventually what you guix people think would be nice to tackle on. (I > think I saw something about a wiki somewhere for example etc.) I=E2=80=99m not sure we need a wiki. :-) A very concrete task that could be of interest to you is the =E2=80=9Cname change=E2=80=9D (a bit of a strong word) that we=E2=80=99d like to implemen= t by 1.0. I=E2=80=99ll try to summarize. Currently we have =E2=80=9CGuix=E2=80=9D an= d =E2=80=9CGuixSD=E2=80=9D, and that confuses things: people visit the web site, they see a =E2=80=9CGuixSD=E2= =80=9D logo and get confused because they were just looking for a package manager, not a whole distro, or they think =E2=80=9CGuixSD=E2=80=9D is a storage device ;-= ), things like that. The idea is to bring everything under the =E2=80=9CGuix=E2=80=9D name. Mos= t of the time, writing =E2=80=9CGuix=E2=80=9D is good enough=E2=80=94after all, one = can run =E2=80=98guix system=E2=80=99 on a foreign distro, too. When we really need to make the distinction, 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. This has implications mostly on the web site and on the manual. Ricardo sketched web site modifications here: https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00300.html It would probably have further implications on how we present Guix/GuixSD. WDYT? > By the way, I wanted to start working on the documentation.=20 > IMHO, it might benefit from a little graphical enhancement for > newcomers. The thing is that it's currently hosted on > gnu.org so it's probably not possible to modify the design. So I wanted > to ask, first, if that's something that would be welcome? What could be > the possibilities? And what would be the technical limitations? The HTML pages at gnu.org/s/guix/manual are generated from Texinfo. The CSS there is shared with all the GNU manuals, which is nice for consistency. Ideally modifications of the CSS would be submitted to the GNU webmaster or bug-gnulib@gnu.org (I forgot which one). However, be aware that you may encounter misplaced conservatism if you take that route, so don=E2=80=99t lose your hair on it. Thanks, Ludo=E2=80=99.