[tc][election] candidate question: strategic leadership

Jim Rollenhagen jim at jimrollenhagen.com
Fri Feb 22 18:45:17 UTC 2019


On Thu, Feb 21, 2019 at 7:56 AM Doug Hellmann <doug at doughellmann.com> wrote:

>
> With the changes at the Foundation level, adding new OIPs, a few board
> members have suggested that this is an opportunity for the TC to evolve
> from providing what some have seen as tactical management through
> dealing with day-to-day issues to more long-term strategic leadership
> for the project. This theme has also come up in the recent discussions
> of the role of the TC, especially when considering how to make
> community-wide technical decisions and how much influence the TC should
> have over the direction individual projects take.
>
> What do you think OpenStack, as a whole, should be doing over the next
> 1, 3, and 5 years? Why?
>

I didn't really think about it much until Chris' first set of TC questions,
but like I said there, I would like the TC to take a more hands-on role
in solving large technical problems in OpenStack. We should be looking to
the
user and operator communities to see what their true pain points are - the
things that wake support up at 2am. It probably isn't mutable config,
tempest
plugin structure, or identity configuration, as awesome as those are. We
should be looking at the problems that seem insurmountable; if we don't, who
else will? I'm not sure if the TC should prescribe solutions or simply
work with projects to explore them, but I suspect the former may be the most
technically beneficial to OpenStack in the long run. I'm not sure what that
would do to the community, though - is it worth it if it causes rifts there?

As far as what OpenStack should be doing - I believe we should put more
focus
on these operational problems. Since feature work seems to have slowed down
some since the peak of the hype cycle, we should be able to manage making
large changes underneath ongoing work. From what I've seen in the wider tech
community, there's a sizable cohort of people who have tried OpenStack and
now recommend against it when folks ask. Let's create less of these people,
and maybe even gain some back. :)

I don't have specific items that I think we should address in the given time
frames, as I haven't done enough research to be able to say.

// jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190222/9181f6f2/attachment.html>


More information about the openstack-discuss mailing list