unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [ART] Updated SLiM theme with GuixSD logo
Date: Fri, 13 Feb 2015 10:46:30 +0100	[thread overview]
Message-ID: <87mw4i4009.fsf@gnu.org> (raw)
In-Reply-To: <87vbj6n4i2.fsf@mango.localdomain> (Ricardo Wurmus's message of "Thu, 12 Feb 2015 23:34:29 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> - do we really want to use the abbreviation "GuixSD" (rather than the
>   actual name) so prominently?  In my opinion the abbreviation just
>   makes it easier to refer to the system, but it's not like that's the
>   actual name.  As the focus is on offering a GNU system (which just
>   happens to be called Guix System Distribution or GuixSD in ambiguous
>   circumstances) wouldn't it be better to stay with either just the new
>   wildebeest logo or simply the GNU logo?

That’s the feeling that many of us shared several weeks ago, that we
shouldn’t do any branding other than GNU.

OTOH, it’s become clear that we’d have no support in doing that and no
influence over the GNU “brand”; in that sense, we would have to spend a
lot of energy for a result that may be unsatisfying.  I suspect Felipe
reached the same conclusion.

We continue to support GNU obviously, and I hope we can contribute to an
evolution in this area, even if not as directly as initially planned.

Does that make sense?

Ludo’.

  reply	other threads:[~2015-02-13  9:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 18:56 [ART] Updated SLiM theme with GuixSD logo Luis Felipe López Acevedo
2015-02-12 19:39 ` Thompson, David
2015-02-12 19:41 ` Andreas Enge
2015-02-12 21:29   ` Pierre-Antoine Rault
2015-02-12 20:52 ` Daniel Pimentel
2015-02-12 22:34 ` Ricardo Wurmus
2015-02-13  9:46   ` Ludovic Courtès [this message]
2015-02-13 14:48     ` Luis Felipe López Acevedo
2015-02-13 21:27   ` Luis Felipe López Acevedo
2015-02-13 21:29     ` David Thompson
2015-02-13 22:58       ` Ludovic Courtès
2015-03-01 15:14     ` Ludovic Courtès
2015-03-01 16:16       ` felipe.lopez
2015-03-01 20:37         ` Ludovic Courtès
2015-03-01 21:33           ` felipe.lopez
2015-02-12 22:50 ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2015-03-13 10:48 白い熊@相撲道
2015-03-14 14:03 ` Ludovic Courtès
2015-03-14 17:44   ` 白い熊@相撲道
2015-03-15 13:47     ` Ludovic Courtès
2015-03-15 16:25       ` 白い熊@相撲道
2015-03-16  8:52         ` Ludovic Courtès
2015-03-16 11:03           ` 白い熊@相撲道
2015-03-16 13:00             ` 白い熊@相撲道
2015-03-16 17:02             ` Ludovic Courtès
2015-03-16 18:12               ` 白い熊@相撲道
2015-03-16 20:40                 ` Ludovic Courtès
2015-03-16 22:31                   ` 白い熊@相撲道
2015-03-16 22:38                     ` Ludovic Courtès
2015-03-16 22:51                       ` 白い熊@相撲道

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=87mw4i4009.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).