unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: L p R n d n <guix@lprndn.info>
Cc: guix-devel@gnu.org
Subject: Re: Communication and Design at Guix
Date: Sun, 13 Jan 2019 22:50:34 +0100	[thread overview]
Message-ID: <875zus1b2t.fsf@gnu.org> (raw)
In-Reply-To: <cucimywvfeu.fsf@lprndn.info> (L. p. R. n. d. n.'s message of "Thu, 10 Jan 2019 13:57:29 +0100")

Hi,

L  p R n  d n    <guix@lprndn.info> skribis:

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

[...]

>> A very concrete task that could be of interest to you is the “name
>> change” (a bit of a strong word) that we’d like to implement by 1.0.
>> I’ll try to summarize.  Currently we have “Guix” and “GuixSD”, and that
>> confuses things: people visit the web site, they see a “GuixSD” logo and
>> get confused because they were just looking for a package manager, not a
>> whole distro, or they think “GuixSD” is a storage device ;-), things
>> like that.
>>
>> The idea is to bring everything under the “Guix” name.  Most of the
>> time, writing “Guix” is good enough—after all, one can run ‘guix system’
>> on a foreign distro, too.  When we really need to make the distinction,
>> for instance in the manual, we would write “Guix System” to designate
>> what we currently call “GuixSD”.
>
> 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).Here,
> it's more about making GuixSD "disappear" but we could also just rebrand
> GuixSD with some kind of "subtitle": "Guix, the system", derive a logo
> 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 “brand”: Guix.  Then “Guix System”
would be a component of Guix, so to speak, similar to GNOME and its
applications.

>> 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?
>
> Yeah, thinking about GuixSD as a derivative is probably the best way to
> comprehend it. So give it its own leaf page is probably a good idea. I
> would keep all downloads on the same page though and just separate them
> visually. But it depends froms what I said previously.

Sounds reasonable.

Would you like to give it a go?  I suppose the changes to the web site
can be made incrementally, it’s not an all-or-nothing change.  If you’d
like to fiddle with this and you need guidance with the web site
machinery, don’t hesitate to ask on IRC or the ML!

Thanks,
Ludo’.

  parent reply	other threads:[~2019-01-13 22:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès
2019-01-09  6:11   ` swedebugia
2019-01-09 21:45     ` Ludovic Courtès
2019-01-10 12:09       ` L p R n d n
2019-01-10 13:20         ` swedebugia
2019-01-10 14:34         ` Ricardo Wurmus
2019-01-13 21:45           ` Ludovic Courtès
2019-01-14 15:02             ` L p R n d n
2019-01-15 10:36               ` zimoun
2019-01-15 18:03                 ` nly
2019-01-15 22:08                   ` Ricardo Wurmus
2019-01-16 11:00                     ` Giovanni Biscuolo
2019-01-15 22:28               ` Ludovic Courtès
2019-01-14 23:25             ` swedebugia
2019-01-15 13:56               ` Ricardo Wurmus
2019-01-15 17:39                 ` Julien Lepiller
2019-01-15 22:30                   ` Ludovic Courtès
2019-01-10 12:17     ` L p R n d n
2019-01-10 12:57   ` L p R n d n
2019-01-10 14:30     ` Ricardo Wurmus
2019-01-13 21:50     ` Ludovic Courtès [this message]
2019-01-14 14:36       ` L p R n d n
2019-01-15 22:31         ` Ludovic Courtès
2019-01-16 16:31       ` George Clemmer
2019-01-17  0:10         ` swedebugia
2019-01-17 10:58         ` L p R n d n
2019-01-17 11:10           ` Ricardo Wurmus
2019-01-17 14:08             ` swedebugia
2019-01-17 16:24               ` L p R n d n

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=875zus1b2t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    /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).