Open Stack

I'd like to go back to the beginning to clarify something.

On 04/29/2015 02:34 PM, Adam Lawson wrote:
> So I started replying to Doug's email in a different thread but didn't want
> to hi-jack that so I figured I'd present my question as a more general
> question about how voting is handled for the TC.
> 
> Anyway, I find it curious that the TC is elected by those within the
> developer community but TC candidates talk about representing the operator
> community

In my statements I talked about acknowledging the operator community not
representing them. When I speak, I represent myself and my best
understanding of a certain situation, if others find value in the
position I hold, they will let me know.

In my view of what comprises OpenStack, the TC is one point of a
triangle and the operators are an entirely different point. Trying to
get two points of a triangle to be the same thing compromises the
integrity of the structure. Each needs to play its part, not try to be
something it is not.

There have been many helpful comments on how those operators who wish to
contribute to reviews, patches and specs as well as receive ATC status
may do so, for those operators who wish to be acknowledged as
contributors as well as being operators.

Operators have a very useful, very valuable, very necessary perspective
that is not a developer's perspective that needs to be heard and
communicated.

Thierry has made the suggestion that a strong User Committee
representing the voice of the operator would be a good direction here. I
support this suggestion. Tim Bell is working on an etherpad here:
https://etherpad.openstack.org/p/YVR-ops-user-committee

Thank you Adam,
Anita.


> who are not allowed to vote. Operators meaning Admins,
> Architects, etc. It sounds like this is something most TC candidates want
> which most would agree is a good thing. At least I think so. ; )
> 
> Is it be feasible to start allowing the operator community to also cast
> votes for TC candidates? Is the TC *only* addressing technical concerns
> that are relevant to the development community? Since the TC candidates are
> embracing the idea of representing more than just the developer community,
> it would /seem/ the voters electing the TC members should include the
> communities being represented. If the TC only addresses developer concerns,
> it would seem they become at risk of losing touch with the
> operator/architecture/user concerns because the operator community voice is
> never heard in the voting booth.
> 
> Perhaps this bumps into how it used to be versus how it should be. I don't
> know. Just struck me as incongruent with the platform of almost every
> candidate - broadening representation while the current rules prohibit that
> level of co-participation.
> 
> Thoughts?
> 
> 
> *Adam Lawson*
> 
> AQORN, Inc.
> 427 North Tatnall Street
> Ste. 58461
> Wilmington, Delaware 19801-2230
> Toll-free: (844) 4-AQORN-NOW ext. 101
> International: +1 302-387-4660
> Direct: +1 916-246-2072
> 
> 
> 
> __________________________________________________________________________
> 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
>