Re: Slonik! - Mailing list pgsql-advocacy
Hi Bryan,
I completely understand, and think it is always a good idea to reflect on how Postgres is perceived based on current branding. My point is that the logo is merely a tool that helps a brand to be recognisable and we risk losing that if we switch to your design. It might be that it is the risk the community willing to take but it's important to recognise it and to understand what we would gain from it.
I am not sure what you mean by scalability?
I think in any case, a variation of an elephant logo might be handy for local conferences or events that are looking for a near-Postgres-logo, but don't have the means to develop it themselves (like those cool graphics that Fabio shared from PGConf.Brasil.)
Kind regards,
Valeria
On Mon, Dec 9, 2019 at 4:15 PM BFarrell915 <bfarrell915@gmail.com> wrote:
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,BryanOn Dec 6, 2019, at 15:24, Valeria Kaplan <vk@dataegret.com> 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>
On Fri, Dec 6, 2019 at 11:46 AM Jan Karremans <jan.karremans@enterprisedb.com> 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, EMEASenior Sales Engineer DACH-RegionEDB 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 <ray@rodonnell.ie> 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
ray@rodonnell.ie
pgsql-advocacy by date: