Hi, I agree that this new updated logo is great refinement to what we
currently have. Love it.
Thanks Heidi
On Mon, Mar 13, 2017 at 8:24 PM, Dan Prince wrote:
> Hi Heidi,
>
> I like this one a good bit better. He might looks a smidge cross-eyed
> to me... but I'd take this one any day over the
Hi Heidi,
I like this one a good bit better. He might looks a smidge cross-eyed
to me... but I'd take this one any day over the previous version.
Thanks for trying to capture the spirit of the original logos.
Dan
On Fri, 2017-03-10 at 08:26 -0800, Heidi Joy Tretheway wrote:
> Hi TripleO team,
Hi all,
Not that it matters one way or the other, Carlos's comment reminded me of
some trivia regarding owl eye color that I had read recently:
https://owlpedia.wordpress.com/2015/08/06/why-do-owls-have-different-colour-eyes/
On Mon, Mar 13, 2017 at 6:16 AM, Carlos Camacho Gonzalez <
ccama...@re
Hey!
Yeahp I think most owls have yellow/orange eyes, this can be a good thing
to try.
Cheers,
Carlos
On Fri, Mar 10, 2017 at 8:53 PM, Dan Sneddon wrote:
> On 03/10/2017 08:26 AM, Heidi Joy Tretheway wrote:
> > Hi TripleO team,
> >
> > Here’s an update on your project logo. Our illustrator tri
On 03/10/2017 08:26 AM, Heidi Joy Tretheway wrote:
> Hi TripleO team,
>
> Here’s an update on your project logo. Our illustrator tried to be as
> true as possible to your original, while ensuring it matched the line
> weight, color palette and style of the rest. We also worked to make sure
> that
On Fri, Mar 10, 2017 at 12:56 PM, Heidi Joy Tretheway <
heidi...@openstack.org> wrote:
> Hi TripleO team,
>
> Here’s an update on your project logo. Our illustrator tried to be as true
> as possible to your original, while ensuring it matched the line weight,
> color palette and style of the rest.
On Fri, Mar 10, 2017 at 12:43 PM, Jiří Stránský wrote:
> On 10.3.2017 17:26, Heidi Joy Tretheway wrote:
>>
>> Hi TripleO team,
>>
>> Here’s an update on your project logo. Our illustrator tried to be as true
>> as
>> possible to your original, while ensuring it matched the line weight,
>> color
>>
On 10.3.2017 17:26, Heidi Joy Tretheway wrote:
Hi TripleO team,
Here’s an update on your project logo. Our illustrator tried to be as true as
possible to your original, while ensuring it matched the line weight, color
palette and style of the rest. We also worked to make sure that three Os in th
Dmitry asked: "I'm late to the party, and I don't really have any strong
opinions about a
TripleO logo, but why is it blue? :) I'm not sure there exist any blue owls.”
Answer: There aren’t any purple porcupines or blue polar bears, either, but the
Barbican and Freezer mascots are in those colo
On 03/10/2017 05:26 PM, Heidi Joy Tretheway wrote:
Hi TripleO team,
Here’s an update on your project logo. Our illustrator tried to be as true as
possible to your original, while ensuring it matched the line weight, color
palette and style of the rest. We also worked to make sure that three Os i
Hey
This version looks awesome, it really feels like what we currently have,
but upgraded xD
I don't see how we can keep the head feathers, so forth,
+1
Thanks Heidi for your effort!
Cheers,
Carlos.
On Fri, Mar 10, 2017 at 5:36 PM, Jason Rist wrote:
> On 03/10/2017 09:26 AM, Heidi Joy T
On 03/10/2017 09:26 AM, Heidi Joy Tretheway wrote:
> Hi TripleO team,
>
> Here’s an update on your project logo. Our illustrator tried to be as true as
> possible to your original, while ensuring it matched the line weight, color
> palette and style of the rest. We also worked to make sure that thr
Hi TripleO team,
Here’s an update on your project logo. Our illustrator tried to be as true as
possible to your original, while ensuring it matched the line weight, color
palette and style of the rest. We also worked to make sure that three Os in the
logo are preserved. Thanks for your patienc
for the same reasons I stated above.
> Thanks,
> Arkady
>
> -Original Message-
> From: Dmitry Tantsur [mailto:dtant...@redhat.com]
> Sent: Friday, February 17, 2017 6:31 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [tripleo] Fwd: TripleO
Message-
From: Dmitry Tantsur [mailto:dtant...@redhat.com]
Sent: Friday, February 17, 2017 6:31 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help
your team?
On 02/17/2017 12:01 AM, Chris Dent wrote:
> On Thu, 16 Feb 2017,
On 2017-02-16 18:43:29 -0800 (-0800), John Dickinson wrote:
[...]
> Second, the foundation messaging around the PTG emphasizes
> per-project developers. From https://www.openstack.org/ptg/
>
> The event is not optimized for non-contributors or people who
> can’t relate to a specific project team.
On 02/17/2017 12:01 AM, Chris Dent wrote:
On Thu, 16 Feb 2017, Dan Prince wrote:
And yes. We are all OpenStack developers in a sense. We want to align
things in the technical arena. But I think you'll also find that most
people more closely associate themselves to a team within OpenStack
than t
On 16 Feb 2017, at 15:01, Chris Dent wrote:
> On Thu, 16 Feb 2017, Dan Prince wrote:
>
>> And yes. We are all OpenStack developers in a sense. We want to align
>> things in the technical arena. But I think you'll also find that most
>> people more closely associate themselves to a team within Op
On Thu, 16 Feb 2017, Dan Prince wrote:
And yes. We are all OpenStack developers in a sense. We want to align
things in the technical arena. But I think you'll also find that most
people more closely associate themselves to a team within OpenStack
than they perhaps do with the larger project. Man
On 2017-02-16 15:20:11 -0500 (-0500), Dan Prince wrote:
[...]
> And there is that rub again. There is implied along with this pressure
> to adopt the new logo. If you don't you'll get a blank space as a sort
> of punishment for going your own way. As Monty said directly... they
> want conformance a
On Thu, Feb 16, 2017 at 3:20 PM, Dan Prince wrote:
> On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote:
>> On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote:
>> [...]
>> > This isn't about aligning anything. It is about artistic control.
>> > The
>> > foundation wants to have icons thei
> On Feb 16, 2017, at 12:20 PM, Dan Prince wrote:
>
> On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote:
>> On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote:
>> [...]
>>> This isn't about aligning anything. It is about artistic control.
>>> The
>>> foundation wants to have icons thei
On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote:
> On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote:
> [...]
> > This isn't about aligning anything. It is about artistic control.
> > The
> > foundation wants to have icons their way playing the "community
> > card"
> > to make those wh
On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote:
[...]
> This isn't about aligning anything. It is about artistic control. The
> foundation wants to have icons their way playing the "community card"
> to make those who had icons they like conform. It is clear you buy into
> this.
>
> Each t
On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote:
> On 02/15/2017 07:54 PM, Dan Prince wrote:
> > At the high level all of this sounds like a fine grand plan: "Help
> > projects create mascots" with a common theme. On the ground level I
> > can
> > tell you it feels a lot more like you are cru
On 02/16/2017 07:25 PM, Heidi Joy Tretheway wrote:
> Amid the spirited discussion on your mascot, I wanted to clear up confusion
> about our next steps and your options.
>
> 1. I’ve taken Carlos’s sketches to our illustration team to ask them to make
> the original TripleO owl in the style of t
Amid the spirited discussion on your mascot, I wanted to clear up confusion
about our next steps and your options.
1. I’ve taken Carlos’s sketches to our illustration team to ask them to make
the original TripleO owl in the style of the new logo family. This takes a bit
of time and probably wo
On Thu, 2017-02-16 at 08:36 -0500, Emilien Macchi wrote:
> I'll shamelessly cross-post here, I didn't know where to reply.
> I agree with Monty and Flavio here.
>
> Heidi has been doing an excellent job in helping OpenStack community
> about $topic, always in the open, which has been very apprecia
On 14/02/17 04:38, Emilien Macchi wrote:
> Team, I've got this email from Heidi.
>
> I see 3 options :
>
> 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
>
> 2. Re-design a new logo that "meets" OpenStack "requirements".
>
> 3. Pick-up the one proposed (see below).
Option
Hi,
Yeah, I tried drafting something based on our current logo and following my
perception about the new foundation styles,
again here are the files (WIP version, is just a PoC)
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.pdf
https://cdn.rawgit.com/cc
On 02/14/2017 03:38 AM, Emilien Macchi wrote:
> Team, I've got this email from Heidi.
>
> I see 3 options :
>
> 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
>
> 2. Re-design a new logo that "meets" OpenStack "requirements".
>
> 3. Pick-up the one proposed (see below).
wh
On 16/02/17 08:36 -0500, Emilien Macchi wrote:
I'll shamelessly cross-post here, I didn't know where to reply.
I agree with Monty and Flavio here.
Heidi has been doing an excellent job in helping OpenStack community
about $topic, always in the open, which has been very appreciated.
We, as a tea
I'll shamelessly cross-post here, I didn't know where to reply.
I agree with Monty and Flavio here.
Heidi has been doing an excellent job in helping OpenStack community
about $topic, always in the open, which has been very appreciated.
We, as a team, have agreed on re-iterating on a new proposal
On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote:
> On 02/15/2017 07:54 PM, Dan Prince wrote:
> > At the high level all of this sounds like a fine grand plan: "Help
> > projects create mascots" with a common theme. On the ground level I
> > can
> > tell you it feels a lot more like you are cru
On 13/02/17 21:38 -0500, Emilien Macchi wrote:
Team, I've got this email from Heidi.
I see 3 options :
1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
2. Re-design a new logo that "meets" OpenStack "requirements".
3. Pick-up the one proposed (see below).
#3
Flavio
P
On 16/02/17 06:36 -0600, Monty Taylor wrote:
On 02/15/2017 07:54 PM, Dan Prince wrote:
At the high level all of this sounds like a fine grand plan: "Help
projects create mascots" with a common theme. On the ground level I can
tell you it feels a lot more like you are crushing the spirit of
creat
On 02/15/2017 07:54 PM, Dan Prince wrote:
> At the high level all of this sounds like a fine grand plan: "Help
> projects create mascots" with a common theme. On the ground level I can
> tell you it feels a lot more like you are crushing the spirit of
> creativity and motivation for some of us.
Ha
Hi Dan, I’m hoping these answers help, and I’m open to continuing the
conversation if you’d like.
> 6 months or so ago we were presented with a new owl from the
> foundation... which had almost none of the same qualities as the
> original. Many of us took a survey about that and provided feedbac
At the high level all of this sounds like a fine grand plan: "Help
projects create mascots" with a common theme. On the ground level I can
tell you it feels a lot more like you are crushing the spirit of
creativity and motivation for some of us.
What's in a mascot? I dunno. Call it a force of moti
On 2017-02-15 16:54:17 -0500 (-0500), Dan Prince wrote:
> I was off earlier this week (and unfortunately couldn't attend the
> weekly meeting) but from the sound of it a very different conclusion
> has been reached within the TripleO community. Apparently, this was
> understood to mean that we *cou
I was off earlier this week (and unfortunately couldn't attend the
weekly meeting) but from the sound of it a very different conclusion
has been reached within the TripleO community. Apparently, this was
understood to mean that we *could not* keep our existing logo. And that
is sad thing to do "jus
Hi Dan,
I’m glad you asked! The value of creating a family of logos is in communicating
that OpenStack projects work together. While the some of the designs of the
existing mascots were great, none of them looked like they were part of the
same family, and that sent a message to the market that
On 2017-02-15 15:52:30 -0500 (-0500), Dan Prince wrote:
> The fact that the foundation is involved in "streamlining" team logos
> just kind of makes me a bit sad I guess. I mean, what value is this
> really adding to the OpenStack projects?
>
> Devs on many projects spend their own time on creatin
The fact that the foundation is involved in "streamlining" team logos
just kind of makes me a bit sad I guess. I mean, what value is this
really adding to the OpenStack projects?
Devs on many projects spend their own time on creating logos... that
they like. I say let them be happy and have their
On Tue, 2017-02-14 at 13:30 +0100, Carlos Camacho Gonzalez wrote:
> I'll vote also for option 1 if we can keep it.
>
> One thing, you can see how designers have iterated over ironic's logo
> http://lists.openstack.org/pipermail/openstack-
> dev/attachments/20170201/a016f685/attachment.png to fit t
Option #1 keep it.
Dan
On Mon, 2017-02-13 at 21:38 -0500, Emilien Macchi wrote:
> Team, I've got this email from Heidi.
>
> I see 3 options :
>
> 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
>
> 2. Re-design a new logo that "meets" OpenStack "requirements".
>
> 3. Pick-
Hi TripleO team,
We can definitely find a middle ground here. Thanks so much for the feedback.
I’ll send these examples on to the illustrators and I think we can make it
work. I appreciate your willingness to compromise!
> On Feb 14, 2017, at 8:57 AM, Carlos Camacho Gonzalez
> wrote:
>
> He
Hello Heidi,
I think most of us already agreed on the fact that our current logo was
created by developers and we like it.
The idea should be to iterate over our current logo to make it fit the
foundation guidelines.
I don't think is hard to do it, I can give you some examples (***The owl
colors
Heidi,
TripleO team discussed about the logo this morning during our weekly meeting.
We understood that we had to change our existing logo because it
doesn't meet OpenStack themes requirements, and that's fine.
Though we would like you to re-iterate on a new logo that would be a
variation on the
I'll vote also for option 1 if we can keep it.
One thing, you can see how designers have iterated over ironic's logo
http://lists.openstack.org/pipermail/openstack-dev/
attachments/20170201/a016f685/attachment.png to fit the OpenStack
illustration style.
Is it possible for designers to iterate ov
Hi,
FWIW, I prefer the existing logo. There are several valid practical reasons
why it would be good to keep it, but I also just like it better.
On Mon, Feb 13, 2017 at 11:08 PM, Emilien Macchi wrote:
> Team, I've got this email from Heidi.
>
> I see 3 options :
>
> 1. Keep existing logo: http:
Hi,
Just a FYI, we have had similar discussions about the proposed logo for
Ironic, there's still many unanswered questions but, if you guys are
interested this is the link to the ML thread:
http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html
Cheers,
Lucas
On Tue, Feb 14
Team, I've got this email from Heidi.
I see 3 options :
1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
2. Re-design a new logo that "meets" OpenStack "requirements".
3. Pick-up the one proposed (see below).
Personally, I would vote for keeping our existing logo (1.) unles
53 matches
Mail list logo