Open Stack

HTML: https://anticdent.org/tc-report-18-26.html

All the bits and pieces of OpenStack are interconnected and
interdependent across the many groupings of technology and people.
When we plan or make changes, wiggling something _here_ has
consequences over _there_. Some intended, some unintended.

This is such commonly accepted wisdom that to say it risks being a
cliche but acting accordingly remains hard.

This
[morning](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-26.log.html#t2018-06-26T09:09:57)
Thierry and I had a useful conversation about the [Tech Vision
2018 etherpad](https://etherpad.openstack.org/p/tech-vision-2018).
One of the issues there is agreeing on what we're even talking
about. How can we have a vision for a "cloud" if we don't agree what
that is? There's hope that clarifying the vision will help unify
and direct energy, but as the discussion and the etherpad show,
there's work to do.

The lack of clarity on the vision is one of the reasons why
Adjutant's [application to be
official](https://review.openstack.org/#/c/553643/) still has [no
clear outcome](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-19.log.html#t2018-06-19T18:59:43).

Meanwhile, to continue [last week's theme](/tc-report-18-25.html),
the TC's role as listener, mediator, and influencer lacks
definition.

Zane wrote up a blog post explaining the various ways in which the
OpenStack Foundation is [expanding](https://www.zerobanana.com/archive/2018/06/14#osf-expansion).
But this raises
[questions](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-20.log.html#t2018-06-20T15:41:41)
about what, if any, role the TC has in that expansion. It appears
that the board has decided to not to do a [joint leadership
meeting](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-21.log.html#t2018-06-21T16:32:17)
at the PTG, which means discussions about such things will need to
happen in other media, or be delayed until the next summit in
Berlin.

To make up for the gap, the TC is
[planning](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-21.log.html#t2018-06-21T16:54:43)
to hold [a gathering](http://lists.openstack.org/pipermail/openstack-tc/2018-June/001510.html)
to work on some of the much needed big-picture and
shared-understanding building.

While that shared understanding is critical, we have to be sure that
it incorporates what we can hear from people who are not long-term
members of the community. In a long discussion asking if [our
tooling makes things harder for new
contributors](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-21.log.html#t2018-06-21T15:21:24)
several of us tried to make it clear that we have an incomplete
understanding about the barriers people experience, that we often
assume rather than verify, and that sometimes our interest in and
enthusiasm for making incremental progress (because if iterating in
code is good and just, perhaps it is in social groups too?) can mean
that we avoid the deeper analysis required for paradigm shifts.

-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent