Open Stack

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/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.svg
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.svg

Again, don't hesitate on pinging me if you think I can help you solve this
:)

Cheers,
Carlos.



On Thu, Feb 16, 2017 at 2:49 PM, Giulio Fidente <gfidente at redhat.com> wrote:

> 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).
>
> while not the most skilled around, I can tell I have seen tripleo
> changing a lot over time, the project, not the logo, so I wouldn't ever
> think of tripleo people as hostile to changes
>
> I'd vote for option (1) as well but if someone could iterate over the
> *existing* logo to make it meet the requirements, instead of proposing a
> new one completely different, that would be received better I think; is
> this still an option? I think Carlos (in CC) suggested something like
> that too?
>
> also, to propose a change I think it would be useful to share the (new?)
> requirements as well, so that people can eventually understand those
> better too
> --
> Giulio Fidente
> GPG KEY: 08D733BA
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170216/59022c2d/attachment.html>