Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iefRX-00079e-Af for pgsql-advocacy@arkaria.postgresql.org; Tue, 10 Dec 2019 13:20:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iefRV-0002rj-DH for pgsql-advocacy@arkaria.postgresql.org; Tue, 10 Dec 2019 13:20:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iefRV-0002rc-0C for pgsql-advocacy@lists.postgresql.org; Tue, 10 Dec 2019 13:20:45 +0000 Received: from mail-io1-xd42.google.com ([2607:f8b0:4864:20::d42]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iefRR-000787-8b for pgsql-advocacy@postgresql.org; Tue, 10 Dec 2019 13:20:44 +0000 Received: by mail-io1-xd42.google.com with SMTP id z23so18676015iog.11 for ; Tue, 10 Dec 2019 05:20:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dataegret-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z9/YLoNU8N2tSV7Pc7+E4lRlvRjy3zAI/Wvq4supxkQ=; b=IW1n97BARrHYUlqS8af6dCzhh7HpntFZE8xluBMlQ9Nij/b7x1gsdABv1+WdmzvcRO 0mfyrQtu6kcstycT2SXfNCo8vcquMS1q0krYkw0lnuVk2psemYE/71ZbhVDUFDY2jKp8 5QOZ3mNu4pJNHgxJrYH7HMljekEbdR4SeoQWXltR3iKB8eFlRggs9zXYeNQhnBa0Bjux u1S4jK2pkMmOezvo3PtqRAfCbbHhzC0i8/2mkwAjfffGPXJhlN/L0ywFAPW3MB62OsJw roFT94pQ8ucI13IqsTFdrMKKdB1MgNYtCMtp0tS3vzBIgxqwzykeO6tcPAtXFk8RP4KN smVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z9/YLoNU8N2tSV7Pc7+E4lRlvRjy3zAI/Wvq4supxkQ=; b=rmVL3A6R8EvK/U+aQ7IcOC4MrY4yqH3xl+WrD5qqgkdKWEG071XZR1kD5fgO6NkLU9 3nqlYX1WS9FQ0umCUhDTewmDsMhRLC/9y5s4FPczI2aCRuZo6TVuBnG537gv1NliR0SN 5yJYgiEMiYn3EpvMkVd3Sg3tOOxuhnNlQlwaYRiZLjEgBrOZzRn3CObliQWO1K/Gs4G2 XfCoclOArvJNE2iJyOnY8FiM9NnosPVXJQuYK6r4ffy8H5pVedj4IOC393kF968kqXT2 zoyYQsKnRbxcLNEiHM23m0By5IrPm9IdVH1VYniHjk4rILS6oyDS/BDjeC1egafSDGBy 2YXQ== X-Gm-Message-State: APjAAAXU8tWzRmaiL6lLCRUxvVlU9SWeRJJwWTiCeZXRZG+ydtVt7P5H j9vTVJodUv+08/vwKP5R8wjHorpVwSiVCJnr2f6aiA== X-Google-Smtp-Source: APXvYqxFtF0ck2uQxbL5vM10Jdo7bs2gEFpj+5L70LSadl1uyBGwzwiInO7hp3K//ufwniR+VKq5FQKTzrGd/DgnvXQ= X-Received: by 2002:a02:820f:: with SMTP id o15mr20987854jag.19.1575984039139; Tue, 10 Dec 2019 05:20:39 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Valeria Kaplan Date: Tue, 10 Dec 2019 13:20:28 +0000 Message-ID: Subject: Re: Slonik! To: BFarrell915 Cc: pgsql-advocacy@postgresql.org Content-Type: multipart/alternative; boundary="000000000000d334c70599596051" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000d334c70599596051 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 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=E2=80=99t think i= t can hurt > to spark a conversation. > > Reguards, > Bryan > > On Dec 6, 2019, at 15:24, Valeria Kaplan wrote: > > =EF=BB=BF > 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 > > > > > > > > > > > > > > > > > > > > *Valeria Kaplan* Marketing Director > > > *Data Egret* > M.: +44 7876 572323 <+44%207876%20572323> > vk@dataegret.com > > > 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=C3=9F, kind regards, >> >> >> >> >> 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=C3= =B6=C3=9Fe >> 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 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 >> >> >> >> --000000000000d334c70599596051 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Bryan,

=
I completely understand, and think=C2=A0it is always a good idea= to reflect on how Postgres is perceived=C2=A0based on current branding. My= point is that the logo is merely a tool that helps a brand to be recognisa= ble and we risk losing=C2=A0that if we switch to your=C2=A0design. It might= be that it is the risk the community willing to take but it's importan= t to recognise it and to understand what we would gain from it.
<= br>
I am not sure what you mean by=C2=A0scalability?
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 coo= l graphics that Fabio shared from PGConf.Brasil.)=C2=A0

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 te= st 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.<= /div>

It may very well be that there is no need for a lo= go redesign! But I do feel my design does have some advantages over the cur= rent 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=E2= =80=99t think it can hurt to spark a conversation.=C2=A0

Reguards,
Bryan

On Dec 6, 2019, at 15:24, Valeria Kaplan <vk@dataegret.com> wrote:

=EF=BB=BF
Thank you for developing it, Bryan!
<= div>
The first question I had seeing this, what are we trying= to achieve=C2=A0by creating a new logo for Postgres. I think current logo = established itself well and is very recognisable among other logos in the i= ndustry. 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).=C2=A0

Overall, I th= ink that if there is a feeling in the community=C2=A0that we need to addres= s a particular issue in Postgres perception and this logo would be part of = a larger change (in the community or the database=C2=A0itself) then a revis= ion of the logo may be=C2=A0justified.=C2=A0

= Kind regards,
Valeria

<Scr= eenshot 2019-12-06 at 22.03.01.png>

<Screenshot 20= 19-12-06 at 22.04.59.png>
<Screenshot 2019-12-06 at 22.00.0= 5.png>
<Screenshot 2019-12-06 at 21.57.25.png>









=C2=A0=C2=A0

Valeria Kaplan=
Marketing Director


Data Egret

M.:=C2=A0+44 7876 572323
vk@dataegret.com


On Fri, Dec 6, 2019 at 11:46 AM = Jan Karremans <jan.karremans@enterprisedb.com> wrote:
Would we see this as an addi= tional logo the the stylist elephant we have now?
As we could have two = different ones, I guess.

Mit freundlichem Gru=C3=9F, kind= regards,

<= /span>
<uc.png&g= t;


= Jan Karrem= ans
Director of Sales Engineering, EMEA=
Senior Sales En= gineer DACH-Region
EDB Postgres Advanced Server=C2=A0Professional
-- Postgres Everywhere --

- Deutsch ist nicht meine Muttersprache,=C2=A0bitte verzeihen Sie Ver= st=C3=B6=C3=9Fe gegen die=C2=A0Rechtschreibung -

Office:=C2=A0=C2=A0+49-(0)3= 222-1097 907
Mobile:=C2=A0+31-(0)6-1638 9607

http://www.enterprisedb.com/

Don't w= alk behind me; I may not lead.
Don't walk in front of me; I= may not follow.
Just walk beside me=C2=A0and be my fri= end.
+*+ Albert Camus +*+

On 6 Dec 2019, at 10:31, Ray O'= Donnell <ray@rodon= nell.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.=C2=A0

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 h= appy 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 bla= ck-and-white contexts.

I wouldn't mind seeing a little more cont= rast in the logo, perhaps some
subtle areas of darker tone that would ma= ke the elephant more obvious.
Though I'm not a design expert...!
=
Ray.

--
Raymond O'Donnell // Galway // Ireland
ray@rodonnell.ie


--000000000000d334c70599596051--