Open Stack

This is the (alegedly) weekly summary of work being done by the
Technical Committee members. The full list of active items is managed in
the wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker

We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/project/923

== Recent Activity ==

It has been 4 weeks since the last update email, in part due to the
Summit, then a holiday, then my absense due to illness.

Project updates:

* Add tenks under Ironic: https://review.openstack.org/#/c/600411/
* Add os_placement role to OpenStack Ansible: https://review.openstack.org/#/c/615187/
* Retired openstack-ansible-os_monasca-ui https://review.openstack.org/#/c/617322/
* Chris Hoge was made the new Loci team PTL https://review.openstack.org/#/c/620370/

Other updates:

* Thierry has been working on a series of changes on behalf of the
  release management team to record the release management style used
  for each deliverable listed in the governance
  repository. https://review.openstack.org/#/c/613268/
* Zane updated our guidelines for new projects to clarify the scoping
  requirements: https://review.openstack.org/#/c/614799/
* Zane also added a Vision for OpenStack Clouds document, describing
  what we see as the scope of OpenStack overall:
  https://review.openstack.org/#/c/592205/
* I copied some code we had in a couple of other places into the
  governance repository to make it easier for the release, goal, and
  election tools to consume the governance data using the new
  openstack-governance library from
  PyPI. https://review.openstack.org/#/c/614599/
* I started a document describing the responsibilities of the TC
  chair. https://review.openstack.org/#/c/618810/

== TC Meetings ==

In order to fulfill our obligations under the OpenStack Foundation
bylaws, the TC needs to hold meetings at least once each quarter. We
agreed to meet monthly, and to emphasize agenda items that help us move
initiatives forward while leaving most of the discussion of those topics
to the mailing list. The agendas for all of our meetings will be sent to
the openstack-dev mailing list in advance, and links to the logs and
summary will be sent as a follow up after the meeting.

Our most recent meeting was held on 6 Dec 2018.

* http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000696.html

The next meeting will be 3 December @ 1400 UTC in #openstack-tc

== Ongoing Discussions ==

We have several governance changes up for review related to deciding how
we will manage future Python 3 upgrades (including adding 3.7 and
possibly dropping 3.5 during Stein). These are close to being approved,
with some final wording adjustments being made now.

* Explicitly declare stein supported runtimes:
  https://review.openstack.org/#/c/611080/
* Resolution on keeping up with Python 3 releases:
  https://review.openstack.org/#/c/613145/

I proposed an update to our house rules to allow faster approval of
release management metadata maintained in the governance repository.

* https://review.openstack.org/#/c/622989/

Thierry and Chris have been working on a description of the role of the
TC.

* https://review.openstack.org/#/c/622400/

Ghanshyam has proposed an enhancement to the Vision for OpenStack Clouds
to cover feature discovery.

* https://review.openstack.org/#/c/621516/

Lance has proposed an update to the charter to clarify how we will
handle PTL transitions in the middle of a development cycle.

* https://review.openstack.org/#/c/620928/

== TC member actions/focus/discussions for the coming week(s) ==

We have several significant changes up for review. Please take time to
consider all of the open patches, then comment and vote on them. It's
very difficult to tell if we have reached consensus if everyone waits
for the conversation to settle before commenting.

== Contacting the TC ==

The Technical Committee uses a series of weekly "office hour" time
slots for synchronous communication. We hope that by having several
such times scheduled, we will have more opportunities to engage
with members of the community from different timezones.

Office hour times in #openstack-tc:

- 09:00 UTC on Tuesdays
- 01:00 UTC on Wednesdays
- 15:00 UTC on Thursdays

If you have something you would like the TC to discuss, you can add
it to our office hour conversation starter etherpad at:
https://etherpad.openstack.org/p/tc-office-hour-conversation-starters

Many of us also run IRC bouncers which stay in #openstack-tc most
of the time, so please do not feel that you need to wait for an
office hour time to pose a question or offer a suggestion. You can
use the string "tc-members" to alert the members to your question.

You will find channel logs with past conversations at
http://eavesdrop.openstack.org/irclogs/%23openstack-tc/

If you expect your topic to require significant discussion or to need
input from members of the community other than the TC, please start a
mailing list discussion on openstack-discuss at lists.openstack.org and
use the subject tag "[tc]" to bring it to the attention of TC members.

-- 
Doug