From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: Andrew Ardill <andrew.ardill@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Our official home page and logo for the Git project
Date: Sat, 12 Apr 2014 06:28:41 +0200 [thread overview]
Message-ID: <5348C0F9.2000208@alum.mit.edu> (raw)
In-Reply-To: <xmqqr453sm76.fsf@gitster.dls.corp.google.com>
On 04/11/2014 09:25 PM, Junio C Hamano wrote:
> [...]
> The motion is about this:
>
> Outside people, like the party who approached us about putting
> our logo on their trinket, seem to associate that logo we see on
> git-scm.com today with our project, but we never officially said
> it was our logo (we did not endorse that git-scm.com is our
> official home page, either, for that matter).
>
> It is silly for us to have to say "Ehh, that is a logo that was
> randomly done and slapped on git-scm.com which is not even our
> official home page, and the logo is licensed CC-BY by somebody
> else. Go talk to them.", every time such a request comes.
>
> Please help us by letting us answer "Yup, that is a logo (among
> others) that represents our project, and we are OK with you
> using it to help promote our project" instead.
+1
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2014-04-12 4:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 18:44 Our official home page and logo for the Git project Junio C Hamano
2014-04-09 14:54 ` Matthieu Moy
2014-04-09 16:43 ` Felipe Contreras
2014-04-10 0:24 ` Andrew Ardill
2014-04-10 7:32 ` David Kastrup
2014-04-11 11:32 ` Javier Domingo Cansino
2014-04-11 16:58 ` Tim Chase
2014-04-11 11:40 ` Jeff King
2014-04-11 12:39 ` Max Horn
2014-04-11 13:29 ` Felipe Contreras
2014-04-11 15:02 ` Max Horn
2014-04-11 15:21 ` Felipe Contreras
2014-04-11 18:37 ` Max Horn
2014-04-11 18:56 ` Felipe Contreras
2014-04-11 19:24 ` Max Horn
2014-04-11 20:26 ` Felipe Contreras
2014-04-11 15:39 ` Philippe Vaucher
2014-04-11 15:48 ` Philippe Vaucher
2014-04-11 16:52 ` Holger Hellmuth
2014-04-11 17:21 ` Felipe Contreras
2014-04-11 18:35 ` Max Horn
2014-04-11 13:24 ` Felipe Contreras
2014-04-11 13:44 ` David Kastrup
2014-04-11 14:09 ` Vincent van Ravesteijn
2014-04-11 15:22 ` Felipe Contreras
2014-04-12 12:34 ` Jeff King
2014-04-12 14:02 ` Felipe Contreras
[not found] ` <CALZVapkdr5R8h3XWwmo3LHEXnMrOQhzVCw2LwP5oRbJ=MVnbUg@mail.gmail.com>
2014-04-13 8:53 ` Javier Domingo Cansino
2014-04-14 8:28 ` Stefan Beller
2014-04-20 17:53 ` Felipe Contreras
2014-04-11 19:25 ` Junio C Hamano
2014-04-11 19:38 ` Jonathan Nieder
2014-04-11 19:45 ` Ronnie Sahlberg
2014-04-11 21:25 ` Brandon McCaig
2014-04-12 4:28 ` Michael Haggerty [this message]
2014-04-12 12:05 ` Jeff King
2014-04-14 13:39 ` Erik Faye-Lund
2014-04-11 16:24 ` Michael Haggerty
2014-04-11 17:07 ` Karsten Blees
2014-04-11 17:20 ` David Kastrup
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=5348C0F9.2000208@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=andrew.ardill@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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.
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 NNTP newsgroup(s).