[openstack-dev] [tc] [all] TC Report 18-28

Chris Dent cdent+os at anticdent.org
Tue Jul 10 13:52:30 UTC 2018


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

With feature freeze approaching at the end of this month, it seems
that people are busily working on getting-stuff-done so there is not
vast amounts of TC discussion to report this week.

Actually that's not entirely true. There's quite a bit of
interesting discussion in [the
logs](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/) but
it ranges widely and resists summary. If you're a fast reader, it
can be pretty straightforward to read the whole week.

Some highlights:

## Contextualizing Change

The topics of sharing personal context, creating a new technical
vision for OpenStack, and trying to breach the boundaries between
the various OpenStack sub-projects flowed in amongst one another.

In a vast bit of background and perspective sharing, Zane provided
his feelings on [what OpenStack ought to
be](http://lists.openstack.org/pipermail/openstack-dev/2018-July/132047.html).
While long, such things help provide much more context to
understanding some of the issues. Reading such things can be effort,
but they fill in blanks in understanding, even if you don't agree.

Meanwhile, and related, there are [continued
requests](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-06.log.html#t2018-07-06T15:20:50)
for nova to engage in orchestration, in large part because there's
nothing else commonly available to do it and while that's true we
can't serve people's needs well.

Some have said that the need for orchestration could in part be
addressed by breaking down some of the boundaries between projects
but [which boundaries is unclear](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-04.log.html#t2018-07-04T01:12:27). 
Thierry says we should [organize work based on
objectives](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-04.log.html#t2018-07-04T08:33:44).

## Goals of Health Tracking

In [last week's report](/tc-report-18-27.html) I drew a connection
between the [removal of diversity
tags](https://review.openstack.org/#/c/579870/) and the [health
tracker](https://wiki.openstack.org/wiki/OpenStack_health_tracker).
This [created
some](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-05.log.html#t2018-07-05T15:29:01)
concern that there were going to be renewed evaluations of projects
that would impact their standing in the community and that these
evaluations were going to be too subjective.

While it is true that the health tracker is a subjective review of
how a project is doing, the evaluation is a way to discover and act
on opportunities to help a project, not punish it or give it a black
mark.

It is important, however, that the TC is making an [independent
evaluation](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-07-05.log.html#t2018-07-05T15:45:59).
-- 
Chris Dent                       ٩◔̯◔۶           https://anticdent.org/
freenode: cdent                                         tw: @anticdent


More information about the OpenStack-dev mailing list