Open Stack

Hi All,

I agree with the items pointed out in the previous mails in the thread.

In my view the discussion on the vision was crucial in order to synchronize on what we think OpenStack is and to understand what direction we would like it to move and how we keep it an innovative environment that fits into the ecosystem around. It is also important to revisit the mission time to time and shape it to how the technology and ecosystem around us evolves.

The discussion about new languages is also pointing towards being inclusive and diverse in technology which is a very important step to keep OpenStack current and flexible and to support the integration engine nature of it on the way forward.

However, to pick my choice, I would like to take a step away from technology and mention the decision on dropping the weekly meetings and using the mailing list and setting up an IRC channel and office hours for the TC. I think it is just as important if not slightly more than the technology itself to be critical and innovative with our processes too within the community to ensure that we are open and inclusive in practice as well.

This might be one of the reasons to have such good diversity among the candidates this time around which shows we are moving to the right direction and is also encouraging as we need all the voices and different points of view, experience and expertise represented in the technical leadership of our community.

Thanks and Best Regards,
Ildikó
(IRC: ildikov)


> On 2017. Oct 13., at 6:49, Swapnil Kulkarni (coolsvap) <me at coolsvap.net> wrote:
> 
> On Fri, Oct 13, 2017 at 1:12 AM, Clay Gerrard <clay.gerrard at gmail.com> wrote:
>> I like a representative democracy.  It mostly means I get a say in which
>> other people I have to trust to think deeply about issues which effect me
>> and make decisions which I agree (more or less) are of benefit to the social
>> groups in which I participate.  When I vote IRL I like to consider voting
>> records.  Actions speak louder blah blah.
>> 
>> To candidates:
>> 
>> Would you please self select a change (or changes) from
>> https://github.com/openstack/governance/ in the past ~12 mo or so where they
>> thought the outcome or the discussion/process was particular good and
>> explain why you think so?
>> 
>> It'd be super helpful to me, thanks!
>> 
>> -Clay
>> 
>> __________________________________________________________________________
>> 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
>> 
> 
> I have few of them on my mind.
> 
> Setting up guidelines for managing releases of binary artifacts [1]
> was very important in and key to the hearts of most OpenStack
> operators and everyone who's looking at the next big leap with
> containerized deployment.
> 
> Embracing new languages in OpenStack which are required as dependency
> for certain projects [2] [3] is a very important decision and I would
> really like to see it through. While there is a lot of work to be done
> to get something fully operational in current infrastructure but as we
> will have more contributors who feel the need, we have the background
> work ready for it.
> 
> And of course setting up the vision and mission for TC [4] was one of
> the important things done. There will still be updates to it, but the
> current draft is a piece of work with a diverse community like ours.
> 
> [1] https://review.openstack.org/#/c/469265/
> [2] https://review.openstack.org/#/c/451524/
> [3] https://review.openstack.org/#/c/398875/
> [4] https://review.openstack.org/#/c/453262/
> 
> -- 
> Best Regards,
> Swapnil Kulkarni
> irc : coolsvap
> me at coolsvap dot net
> 
> __________________________________________________________________________
> 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