From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>,
Luis Felipe <luis.felipe.la@protonmail.com>
Cc: "45838@debbugs.gnu.org" <45838@debbugs.gnu.org>
Subject: [bug#45838] website: Add a Cuirass page.
Date: Wed, 13 Jan 2021 20:42:38 +0100 [thread overview]
Message-ID: <86sg74sjwx.fsf@gmail.com> (raw)
In-Reply-To: <87ft34vlil.fsf@gnu.org>
Hi,
On Wed, 13 Jan 2021 at 17:39, Mathieu Othacehe <othacehe@gnu.org> wrote:
> Hey Luis & Ludo,
>
>> If even more people dislike the name, I think it is a good time to consider alternatives before introducing a new image for the project.
>>
>> Don't worry about the current logo. It can be modified or redone.
>
> Thanks for commenting! As much as I would also like to change the name
> of the project, I think now is maybe not the best time.
>
> I will announce soon that NLnet will sponsor some of the work I'm doing
> on Cuirass and changing the name right now could be misleading. Maybe in
> a few months?
From my point of view, it is a bad idea to rename, whatever when. Even
if it is not the greatest name ever, rename would just add confusion and
I do not see any gain (except personal taste).
Why Cuirass for Continuous Integration? Why not! :-) Why Jenkins or
Hudson? Why not.
The logos are really nice! Thanks Luis.
Cheers,
simon
next prev parent reply other threads:[~2021-01-13 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 10:54 [bug#45838] website: Add a Cuirass page Mathieu Othacehe
2021-01-13 15:00 ` Luis Felipe via Guix-patches via
2021-01-13 15:06 ` Ludovic Courtès
2021-01-13 16:08 ` Luis Felipe via Guix-patches via
2021-01-13 16:39 ` Mathieu Othacehe
2021-01-13 17:59 ` Luis Felipe via Guix-patches via
2021-01-13 19:42 ` zimoun [this message]
2021-01-14 11:43 ` Ludovic Courtès
2021-01-14 17:43 ` bug#45838: " Mathieu Othacehe
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sg74sjwx.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=45838@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=othacehe@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.