Open Stack

( HTML at https://anticdent.org/tc-report-50.html )

Several members of the TC were at [KubeCon](http://events.linuxfoundation.org/events/kubecon-and-cloudnativecon-north-america)
last week so there's been limited activity since the [last
report](https://anticdent.org/tc-report-49.html) and, of what has
happened, much of it is related to establishing productive relations
with the Kubernetes community.

## Coping with Strategic Contributions

One of the things that came out of the conversations that happened
with the k8s community is that they too are struggling to deal with
ensuring what ttx describes as strategic contributions: functionality
that is of benefit to the entire community as opposed to features
pushed upstream by corporations to enhance their position or
visibility in the market.

There's some discussion of this on
[Thursday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-07.log.html#t2017-12-07T14:58:20)
and some again [Today
(Tuesday)](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html#t2017-12-12T09:41:59).

I expressed some confusion about the term, as what's strategic is
in the eye of the beholder and the executor, and a mind of a certain
disposition tends towards thinking of _strategic_ contributions as
advancing nefarious gains, and _clearly_ the happy world of open
source would _never_ be nefarious, so it must be corporations.

A positive outcome from the conversations last week is "...we'll push
the respective corporate sponsors of our respective foundations to
report 'how they contribute to the project'". An important
distinction here from other attempts at encouraging long-term, of
benefit to the entire community, contributions is that this would be
human narrative, not numbers. Stories of the ways in which corporate
sponsors have enabled lasting improvements.

Thursday afternoon's
[discussion](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-07.log.html#t2017-12-07T15:18:14)
had some additional details on how and why human curated information
may be most useful for this kind of thing, but there are the usual
constraints of "who will do that?"

## Other KubeCon

There were also summaries from ttx and dhellman on a variety of additional
topics from KubeCon in [today's
log](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html).
Some interesting points in there beyond strategic contributions,
including:

* [dev
   tooling](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html#t2017-12-12T09:35:12)
   (see also [dhellman a bit later in the
   day](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html#t2017-12-12T14:22:59))
* [different styles of
   governance](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html#t2017-12-12T09:53:46)
* [release
   management](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-12.log.html#t2017-12-12T10:03:51)

There are going to be a lot of opportunities for learning and collaborating.
I hope we'll see some further summaries (human narrative!) from the
people who were there.

## Stuck Reviews

There are a couple of governance reviews in progress that need input
from the wider community. As things currently stand they are a bit stuck:

* [Clarify testing for interop programs](https://review.openstack.org/#/c/521602/)
* [Add Storyboard Migration (as a goal) to Rocky](https://review.openstack.org/#/c/513875/)

-- 
Chris Dent                      (⊙＿⊙')         https://anticdent.org/
freenode: cdent                                         tw: @anticdent