public inbox for [email protected]
help / color / mirror / Atom feedFrom: BFarrell915 <[email protected]>
To: Valeria Kaplan <[email protected]>
Cc: Jan Karremans <[email protected]>
Cc: Ray O'Donnell <[email protected]>
Cc: [email protected]
Subject: Re: Slonik!
Date: Mon, 9 Dec 2019 11:15:51 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAPcrru4GoF5YpTBphLskjyxQh0MqyVjbLUvVUFRQsGe+8iG=Fg@mail.gmail.com>
References: <CAPcrru4GoF5YpTBphLskjyxQh0MqyVjbLUvVUFRQsGe+8iG=Fg@mail.gmail.com>
Hi Valeria,
My goal is just to have some fun and test my skills! I saw that old diamond logo and the idea popped into my head. I thought it was at least an interesting idea so I thought I would share.
It may very well be that there is no need for a logo redesign! But I do feel my design does have some advantages over the current logo, namely scalability. The design also has a more modern and sleek look; which may not be the direction PostreSQL wants to take, but I don’t think it can hurt to spark a conversation.
Reguards,
Bryan
>> On Dec 6, 2019, at 15:24, Valeria Kaplan <[email protected]> wrote:
>
> Thank you for developing it, Bryan!
>
> The first question I had seeing this, what are we trying to achieve by creating a new logo for Postgres. I think current logo established itself well and is very recognisable among other logos in the industry. Changing it would mean that we might risk losing this recognition, especially when many Postgres initiatives have logos based on the official Postgres elephant (attached).
>
> Overall, I think that if there is a feeling in the community that we need to address a particular issue in Postgres perception and this logo would be part of a larger change (in the community or the database itself) then a revision of the logo may be justified.
>
> Kind regards,
> Valeria
>
> <Screenshot 2019-12-06 at 22.03.01.png>
>
> <Screenshot 2019-12-06 at 22.04.59.png>
> <Screenshot 2019-12-06 at 22.00.05.png>
> <Screenshot 2019-12-06 at 21.57.25.png>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Valeria Kaplan
> Marketing Director
>
>
> Data Egret
>
> M.: +44 7876 572323
> [email protected]
>
>
>> On Fri, Dec 6, 2019 at 11:46 AM Jan Karremans <[email protected]> wrote:
>> Would we see this as an additional logo the the stylist elephant we have now?
>> As we could have two different ones, I guess.
>>
>> Mit freundlichem Gruß, kind regards,
>>
>> <uc.png>
>>
>>
>> Jan Karremans
>> Director of Sales Engineering, EMEA
>> Senior Sales Engineer DACH-Region
>> EDB Postgres Advanced Server Professional
>> -- Postgres Everywhere --
>>
>> - Deutsch ist nicht meine Muttersprache, bitte verzeihen Sie Verstöße gegen die Rechtschreibung -
>>
>> Office: +49-(0)3222-1097 907
>> Mobile: +31-(0)6-1638 9607
>>
>> http://www.enterprisedb.com/
>>
>> Don't walk behind me; I may not lead.
>> Don't walk in front of me; I may not follow.
>> Just walk beside me and be my friend.
>> +*+ Albert Camus +*+
>>
>>> On 6 Dec 2019, at 10:31, Ray O'Donnell <[email protected]> wrote:
>>>
>>>> On 06/12/2019 04:38, BFarrell915 wrote:
>>>> Hello PostgreSQL advocacy group,
>>>>
>>>> I recently contacted the core team about a logo design I came up with.
>>>> Bruce kindly directed me towards this group.
>>>>
>>>> As you can see in the forwarded message below, logo design is a bit of a
>>>> hobby for me. If you and the community agree that the design has
>>>> potential, I would be happy to iterate on the design based on your feedback.
>>>>
>>>> If not, it was a fun project for me anyway.
>>>
>>> I really like your logo; it's useful too in that it would work equally
>>> well in colour and black-and-white contexts.
>>>
>>> I wouldn't mind seeing a little more contrast in the logo, perhaps some
>>> subtle areas of darker tone that would make the elephant more obvious.
>>> Though I'm not a design expert...!
>>>
>>> Ray.
>>>
>>> --
>>> Raymond O'Donnell // Galway // Ireland
>>> [email protected]
view thread (13+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Slonik!
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox