Front page | perl.perl6.language |
Postings from March 2009
Re: Logo considerations
From: James Fuller
March 24, 2009 15:39
Re: Logo considerations
Message ID: firstname.lastname@example.org
to further comment, I would never believe a logo actually influences
which programming languages one chooses to develop in ... but I would
argue that a logo needs to convey the right 'messages' to those who
pay for software projects ... as with any logo; my point is to
identify these messages prior to instantiation e.g. graphic design ...
though doing both ain't bad either.
here is a stab at some simple messages.
for developers: inclusive, easy to use, fast, powerful, linguistic
based, DIY, all computing paradigms allowed (func, proc, oo, etc),
for wider audience: robust, trusted, straightforward, safe, supported
colors evoke meaning, shapes/animals, etc do as well ...
thats enough from the 'marketing corner' ... back to programming.
cheers, Jim Fuller
On Tue, Mar 24, 2009 at 10:34 PM, Guy Hulbert <email@example.com> wrote:
> On Tue, 2009-24-03 at 21:10 +0100, James Fuller wrote:
>> creating a logo by committee is probably the worst way to design such
>> things ... perl6 logo will be seen in the context of other more
>> professionally designed logos and like it or not using the basics of
> I hate the java stuff (professional). I don't think much of the debian
> stuff either (amateur). Some of the things suggested here have been
> pretty good.
>> Is there any sponsorship money to spend on a very good graphic
>> designer to create something based on a small list of requirements as
>> to what meaning it should convey ?
> How was the parrot logo created ?? I saw a suggestion here that it is
> professionally designed but that wasn't confirmed. It looks good enough
> to me regardless.
> I don't see a problem with a long list ...
>> Of course the logo should represent the community fundamentally, but I
>> find all of the suggestions little to do with addressing needs of a
>> logo versus needs of what I would call more of a 'club' badge.
> ... I see the suggestions here as necessary input.
>> I mention these concerns because I would like perl6 to be adopted to
>> as wide a developer audience as possible.
> I don't think the logo will make much difference.
> I don't particularly care much about *what* the logo is or *how* it is
> created. I've only been offering comments as feedback to the people who
> are actually working on it. Beauty is better than not.
>> my 2p, Jim Fuller