caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Olivier Grisel <olivier.grisel@laposte.net>
To: Benjamin Geer <ben@socialtools.net>,
	"O'Caml Mailing List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Some logo for your OCaml related websites
Date: Sun, 22 Aug 2004 18:54:20 +0200	[thread overview]
Message-ID: <4128CFBC.9000500@laposte.net> (raw)
In-Reply-To: <4128CBB6.4090902@socialtools.net>

[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]

I forward this last mail to the caml-list since I forgot to "replay-all" 
before ...

Benjamin Geer a écrit :
> Olivier Grisel wrote:
> 
>> I feel very sorry butI wasn't aware of the origin of this "Joe Camel" 
>> think.
> 
> 
> It was a huge, very controversial advertising campaign... a lot of 
> people were (and still are) very angry about it, all over the world.
> 
>> I can remove the grass bit to try to break the association with the 
>> Joe Camel.
>>
>> What do you think ?
> 
> 
> I don't think it would help.  The shape of the camel face (even without 
> the sunglasses) is what makes it Joe Camel.  This was the intention of 
> the OCaml team when they chose this logo, apparently as a joke (in very 
> bad taste, I think).
> 
> I think OCaml needs a completely new logo.
> 
> The problem of how to make it different from the Perl logo is 
> interesting.  Actually O'Reilly has a trademark on the use of a camel to 
> represent a programming language:
> 
> http://perl.oreilly.com/usage
> 
> I asked them about this last year, and they said they currently had no 
> position on the use of a camel to represent the OCaml language.  I don't 
> know whether they might eventually cause trouble.  You might want to ask 
> them about it.
> 
> Another alternative would be to make a logo that doesn't represent a 
> camel at all.

I agree. Anybody has a better idea ? What could symobolize the ocaml 
programming language ? OReilly seems to think a horse[1] might do, but 
I'm  not quite so sure :o)

[1] http://web.linuxfr.org/2001/03/05/2585.html

Best,

--
Olivier

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2004-08-22 16:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 15:39 Olivier Grisel
     [not found] ` <4128C40F.60702@socialtools.net>
     [not found]   ` <4128CA04.9020104@laposte.net>
     [not found]     ` <4128CBB6.4090902@socialtools.net>
2004-08-22 16:54       ` Olivier Grisel [this message]
2004-08-23  3:01         ` Brandon J. Van Every
2004-08-23  9:03         ` Damien Doligez
2004-08-23 18:10           ` William D. Neumann
2004-08-23 18:45             ` Sven Luther
2004-08-23 18:45               ` William D. Neumann
2004-08-23 20:05                 ` skaller
2004-08-23 22:24           ` Brian Hurt
2004-08-24 13:58             ` Christophe Raffalli
     [not found] <4129E392.8000407@laposte.net>
2004-08-23 18:45 ` Brandon J. Van Every
     [not found] <Pine.LNX.4.44.0408241131190.5809-100000@localhost.localdomain>
2004-08-24 17:02 ` Olivier Grisel

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=4128CFBC.9000500@laposte.net \
    --to=olivier.grisel@laposte.net \
    --cc=ben@socialtools.net \
    --cc=caml-list@inria.fr \
    /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).