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 appreciated. > > We, as a team, have agreed on re-iterating on a new proposal to find > a > new logo that meets both TripleO devs taste and OpenStack community > needs. That's how we work together. > Unfortunately, this choice won't satisfy everyone and that's fine, > that's how Open Source works I guess.
I don't think I see team agreement here. Was the IRC meeting last Tuesday what we are using as a basis for this agreement. Not everyone was present I think... also I think people are quite busy right now with the upcoming release to be focusing on this discussion right now. Wouldn't it be wise to postpone this a bit and gather a larger sampling of the team feelings before making a consolidated statement like this? Also, before committing to using any option wouldn't it be good to actually see it first? Dan > > So the next steps are clear: let's work with Heidi and her team to > find the best logo for TripleO, and let's all have a Gin Tonic in > Atlanta. > > And folks, that's a logo, I think we'll all survive. > Peace. > > On Thu, Feb 16, 2017 at 7:51 AM, Flavio Percoco <fla...@redhat.com> > wrote: > > 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 > > > > > > > > > > > Personally, I would vote for keeping our existing logo (1.) > > > unless someone > > > has time to create another one or if the team likes the proposed > > > one. > > > > > > The reason why I want to keep our logo is because our current > > > logo was > > > created by TripleO devs, we like it and we already have tee- > > > shirts and > > > other goodies with it. I don't see any good reason to change it. > > > > > > Discussion is open and we'll vote as a team. > > > > > > Thanks, > > > > > > Emilien. > > > > > > ---------- Forwarded message ---------- > > > From: Heidi Joy Tretheway <heidi...@openstack.org> > > > Date: Mon, Feb 13, 2017 at 8:27 PM > > > Subject: TripleO mascot - how can I help your team? > > > To: Emilien Macchi <emil...@redhat.com> > > > > > > > > > Hi Emilien, > > > > > > I’m following up on the much-debated TripleO logo. I’d like to > > > help your > > > team reach a solution that makes them happy but still fits within > > > the > > > family of logos we’re using at the PTG and going forward. Here’s > > > what our > > > illustrators came up with, which hides an “O” shape in the owl > > > (face and > > > wing arcs). > > > > > > https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLf > > > HFa?dl=0 > > > At this point, I don’t have quorum from your team (I got a lot of > > > conflicting feedback, most of which was “don’t like” but not > > > actionable > > > for > > > the illustrators to make a revision). At the PTG, we’ll have > > > mascot > > > stickers and signage for all teams except for Ironic and TripleO, > > > since > > > we’re still waiting on your teams to make a final decision. > > > > > > May I recommend that your team choose one person (or a small > > > group of no > > > more than three) to finalize this? I was able to work through all > > > of > > > Swift’s issues with just a quick 15-minute chat with John > > > Dickinson and > > > I’d > > > like to believe we can solve this for TripleO as well. > > > > > > We know some of your team has expressed concern over retiring the > > > existing > > > mascot. It’s not our intention to make anyone “get rid of” a > > > beloved icon. > > > Your team can certainly print it on vintage items like shirts and > > > stickers. > > > But for official channels like the website, we need a logo to > > > represent > > > TripleO that’s cohesive with the rest of the set. > > > > > > Perhaps when you’re face to face with your team at the PTG, you > > > can > > > discuss > > > and hopefully render a final decision to either accept this as a > > > logo, or > > > determine a few people willing to make any final changes with me? > > > > > > Thanks in advance for your help! > > > > > > > > > [image: photo] > > > *Heidi Joy Tretheway* > > > Senior Marketing Manager, OpenStack Foundation > > > 503 816 9769 | Skype: heidi.tretheway > > > > > > <https://webapp.wisestamp.com/sig_iframe?origin=mac-mail&signatur > > > e_id=5499768844845056&t=0.9726545857097719#> > > > <http://linkedin.com/in/heiditretheway> > > > <http://twitter.com/heiditretheway> > > > <http://www.openstack.org/> > > > > > > > > > > > > > > > > > > > > > -- > > > Emilien Macchi > > > > > > > > > > > _________________________________________________________________ > > > _________ > > > OpenStack Development Mailing List (not for usage questions) > > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:un > > > subscribe > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > -- > > @flaper87 > > Flavio Percoco > > > > ___________________________________________________________________ > > _______ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu > > bscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
