unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>,
	25205@debbugs.gnu.org
Subject: bug#25205: Guix package is using the GuixSD logo instead of the Guix logo
Date: Thu, 15 Dec 2016 22:12:58 +0100	[thread overview]
Message-ID: <87eg187v6t.fsf@gnu.org> (raw)
In-Reply-To: <87wpf1ayro.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 15 Dec 2016 18:27:23 +0100")

Hi,

ludo@gnu.org (Ludovic Courtès) writes:

> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> Steps to reproduce
>> ==================
>>
>> 1. Go to https://www.gnu.org/software/guix/packages/g.html
>> 2. Locate a guix package, and click on the "Expand" button
>>
>>
>> Unexpected behavior
>> ===================
>>
>> The description shows the logotype of the Guix System Distribution.
>
> The list of GNU package logos is maintained separately, in the “GNU
> womb” project at <https://savannah.gnu.org/projects/womb>.  So in
> general such reports should go to bug-womb@gnu.org.
>
> However, I would argue that the original Guix logotype is mostly
> superseded by the other one.  I’ve come to the conclusion that it’s
> confusion to have two logos, and that the GuixSD one is cute anyway.
> :-)

As long as Guix and GuixSD are not synonymous, I would argue that mixing
the two logos increases confusion, whether it looks pretty or not.
Especially since the logos include their name.

If the choice of using GuixSD logo when designing Guix is about
esthetics, maybe we could use the same symbol for both logos.  Maybe
with a slightly different color that would help distinguish them?

What do people think?

-- 
Mathieu Lirzin

  parent reply	other threads:[~2016-12-15 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15 15:32 bug#25205: Guix package is using the GuixSD logo instead of the Guix logo Luis Felipe López Acevedo
2016-12-15 17:27 ` Ludovic Courtès
2016-12-15 20:47   ` Christopher Allan Webber
2016-12-15 21:12   ` Mathieu Lirzin [this message]
2016-12-16  7:00     ` Chris Marusich
2016-12-16  9:48       ` Mathieu Lirzin
2016-12-16 10:28       ` Ludovic Courtès
2016-12-16 15:56         ` Luis Felipe López Acevedo
2016-12-16 16:08           ` Ricardo Wurmus
2016-12-16 21:37             ` Luis Felipe López Acevedo
2016-12-17 14:45             ` Luis Felipe López Acevedo
2016-12-17 17:09               ` Mathieu Lirzin
2016-12-17 18:49               ` Ludovic Courtès
2016-12-17 21:05               ` Chris Marusich
2016-12-18  2:14                 ` Luis Felipe López Acevedo
2016-12-22  0:42 ` Luis Felipe López Acevedo
2016-12-29 17:30   ` Ludovic Courtès
2016-12-22  7:49 ` bug#25205: Guix Wikipedia page logo updated Tobias Geerinckx-Rice
2016-12-29 17:42   ` Ludovic Courtès

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=87eg187v6t.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=25205@debbugs.gnu.org \
    --cc=felipe.lopez@openmailbox.org \
    --cc=ludo@gnu.org \
    /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).