From: "Patrick Monnerat" <Patrick.Monnerat@datasphere.ch>
To: "Keith Seitz" <keiths@redhat.com>, <insight@sourceware.org>
Subject: RE: Request for a larger icon
Date: Tue, 28 Oct 2014 09:52:00 -0000 [thread overview]
Message-ID: <AB5E58B87EB73C46A38073D8F459F113D9FF9F@dataspheresrv01> (raw)
In-Reply-To: <544E939D.5010300@redhat.com>
Keith Seitz wrote:
> However, I see that we're still using GNUPro branding from twenty
years ago but the web site has been changed. I'm not a huge fan of the
web site's logo, but I think it better than using GNUPro all over the
place.
You may be right: I googled for a insight/gdbtk/gnupro logo without
success: I do not have the historical background for insight/gnupro.
> So ideally what size would you like icons?
At least 64x64, but 256x256 would be better. A vectorial icon would be
great (we can instantiate any size). See
https://bugzilla.redhat.com/show_bug.cgi?id=1157545.
> I think I can convince my wife (also a professional graphic designer)
to whip us up some graphics.
This would be great! A professional work is almost always better. So I
won't start a redesign myself.
> How quickly do you need it?
Currently I scale up the existing icon at package build time: this
solution is temporarily acceptable, although not producing the nicest
icon :-|. So I'm not hurry, but the quicker the better.
> PS. No, I haven't forgotten about the git repo! Really!
For now, I periodically adjust the github one. You can start populating
sourceware.org from there: it's better and more recent than the snapshot
I sent you. In any case, a true official repo (with possibly write perms
for me ;-) would be preferable.
Thanks for the reply.
Cheers,
Patrick
prev parent reply other threads:[~2014-10-28 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 13:38 Patrick Monnerat
2014-10-27 18:49 ` Keith Seitz
2014-10-28 9:52 ` Patrick Monnerat [this message]
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=AB5E58B87EB73C46A38073D8F459F113D9FF9F@dataspheresrv01 \
--to=patrick.monnerat@datasphere.ch \
--cc=insight@sourceware.org \
--cc=keiths@redhat.com \
/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.
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).