Open Stack

On Mon, Apr 10, 2017 at 11:16:57AM +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) ? 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 ?

I know personally I'm planning to dedicate more time over the next cycle to TC
activities. Something for me personally that came out of doing the visioning
exercise last month was that it did give me an opportunity to reflect on what
I viewed as priorities for the next 2 years.

So I think for me, as I outlined in the candidacy email, the one initiative I'd
really like to make a push for over the next 6 months is to start working on
trying build up the systems in place to support both part time contributors and
working on growing new leaders in the community. Realistically I don't think
either is completely accomplishable in 6 months, but getting a good start and
making initial progress is.

Thanks,

Matt Treinish
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170412/4fbe665f/attachment.sig>