Open Stack

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

It's a theme of no surprise, but this report, dedicated to ensuring
people are just a bit more informed, has a fair bit to report on how
staying informed can be difficult.

# Global Communication

[Last
Wednesday](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-21.log.html#t2018-03-21T13:12:59),
there was a wide ranging conversation about some of the difficulties
that people living and working in the APAC area, especially China,
experience when trying to interact with all of the OpenStack
community. It's not solely a problem of time zone or language, there
are also institutional limits on access to tools and networks, and
different preferences.

One important question that was raised is that if an organization
that is a member of the OpenStack Foundation (and thus obliged, at
least in spirit, to contribute upstream) is knowingly limiting their
employees access to IRC, email, and other tools of the OpenStack
trade, are they violating the spirit of their agreement to be open?

Notably absent from this discussion were representatives of the
impacted individuals or companies. So there was a lot of speculation
going on.

This topic was picked back up [later in the same
day](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-21.log.html#t2018-03-21T21:32:00),
eventually leading to the idea of extending the [contributors
guide](https://docs.openstack.org/contributors/), which is mostly
for humans, to include a [Contributing Organization
Guide](https://etherpad.openstack.org/p/Contributing_Organization_Guide).
Good idea!

# Stackalytics Tired

Also on Wednesday there was
[discussion](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-21.log.html#t2018-03-21T16:54:13)
of how [Stackalytics](http://stackalytics.com/) may be having some
accuracy problems and whatever shall we do about that? Options
include: kill it, fix it, replace it with something else, or switch
over to a narrative report per cycle.

I'd be inclined to kill it first and see what organically emerges from
the void. However we can't really do that because it's not run by
OpenStack.

# Adjutant

Last Thursday [the
application](https://review.openstack.org/#/c/553643/) of
[Adjutant](https://adjutant.readthedocs.io/) to be an official
OpenStack project was
[discussed](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-22.log.html#t2018-03-22T15:04:01).
There's still a bit of confusion about what it actually does, but to
at least some people it sounds pretty cool.

Debate will continue on the review and if necessary, time will be set
aside at the [Forum](https://wiki.openstack.org/wiki/Forum) to
discuss the project in more detail.

# Elections

[This morning's
topic](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-03-27.log.html#t2018-03-27T09:05:33)
was the forthcoming election for half the TC. There are at least two
incumbents who will not be running for re-election. The office hours
discussion had some interesting things to say about what governance
is and to whom it is relevant.

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