On 10/04/17 11:16 +0200, Thierry Carrez wrote:
Hi everyone,New in this TC election round, we have a few days between nominations and actual voting to ask questions and get to know the candidates a bit better. I'd like to kick off this new "campaigning period" with a basic question on available time and top priority. All the candidates are top community members with a lot of responsibilities on their shoulders already. My experience tells me that it is easy to overestimate the time we can dedicate to Technical Committee matters, and how much we can push and get done in six months or one year. At the same time, our most efficient way to make progress is always when someone "owns" a particular initiative and pushes it through the governance process. So my question is the following: if elected, how much time do you think you'll be able to dedicate to Technical Committee affairs (reviewing proposed changes and pushing your own) ?
I consider my role in the TC to be half of my work in the community. The other half is covered by my other technical contributions. My reviews and proposed changes on the Technical Committee tasks are as "important" (if not more, sometimes) as my contributions to other tasks.
If there was ONE thing, one initiative, one change you will actively push in the six months between this election round and the next, what would it be ?
One thing I'd love to see happening more is to have more bridges built between the OpenStack community and other cloud communities like CNCF. I truly believe there's lots we can learn from each other and share. However, for us to be able to create stable, solid, bridges, we need to think of ourselves as a single community composed by multiple bricks. These bricks can be used as a group or individually but they definitely cooperate between them. Make OpenStack more "programmable/flexible". So, to answer your question directly, I'd choose to focus on improving the OpenStack community by taking the time to check where we are, what we are, where we are headed, how we can there. Documenting this process, the OpenStack culture and making sure the community is in a healthy state team/project wise. I think this would make our existing interactions with other communities better and it'll also help creating new ones. Flavio -- @flaper87 Flavio Percoco
signature.asc
Description: PGP signature
__________________________________________________________________________ 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
