Open Stack

Results of the survey:
https://docs.google.com/forms/d/1Vx9qMRhYxYZE5qYKmU6y7Czr4klBLlRS7ARQFLw4UEo/edit#responses
71% to accept the new logo to be the new mascot, once we've
Fondation's feedback on Carlos's proposal. If some iterations are
needed, we'llwork with them to adjust. But accept that a new logo will
replace the original one.
29% to decline any new logo and keep the original one.

Heidi, do we have any update on what Carlos sent before the PTG? Is
there anything we can do to move forward?


Thanks everyone,

On Fri, Feb 17, 2017 at 9:21 AM,  <Arkady.Kanevsky at dell.com> wrote:
> There is no project that can stand on its own.
> Even Swift need some identity management.
>
> Thus, even if you are contributing to only one project your are still dependent on many others. Including QA and infrastructure and so on.
>
> While most Customers are looking on a few projects together and not all projects combined it is still referred to as OpenStack. The release is of openstack.
> There are a lot of features that span many projects and just because a feature is done in one project it is not sufficient for customer needs. HA, upgrade, log consistency are all examples of it.
>
> The strength of openstack is in combination of projects working together.
>
> I will skip topic what is core and what is not.
> I personally think that we did customer and ourselves a big disservice when we abandon integrated release concept for the same reasons I stated above.
> Thanks,
> Arkady
>
> -----Original Message-----
> From: Dmitry Tantsur [mailto:dtantsur at redhat.com]
> Sent: Friday, February 17, 2017 6:31 AM
> To: openstack-dev at 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, 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. Many of us in TripleO
>>> feel that way I think. This is a healthy thing, being part of a team.
>>> Don't make us feel bad because of it by suggesting that uber
>>> OpenStack graphics styling takes precedent.
>>
>> I'd very much like to have a more clear picture of the number of
>> people who think of themselves primarily as "OpenStack developers"
>> or primarily as "$PROJECT developers".
>>
>> I've always assumed that most people in the community(tm) thought of
>> themselves as the former but I'm realizing (in part because of what
>> Dan's said here) that's bias or solipsism on my part and I really have
>> no clue what the situation is.
>>
>> Anyone have a clue?
>
> I don't have a clue, and I don't personally think it matters. But I suspect the latter is the majority. At least because very few contributors have a chance to contribute to something OpenStack-wide, while many people get assigned to work on a project or a few of them.
>
> That being said, I don't believe that the "OpenStack vs $PROJECT" question is as important as it may seem from this thread :)
>
>>
>>
>>
>> ______________________________________________________________________
>> ____ OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Emilien Macchi