Open Stack

This is the 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 ==

Project updates:

* Add afsmon project under infra, https://review.openstack.org/572527
* Add new roles to OpenStack-Ansible, https://review.openstack.org/572556

Other approved changes:

* document house-rule for chair-proposed typo fixes,
  https://review.openstack.org/572811
* showing PTL and TC email addresses on gov site:
  https://review.openstack.org/#/c/575554/2 and
  https://review.openstack.org/#/c/575797/2
* the principle "We Value Constructive Peer Review":
  https://review.openstack.org/#/c/570940/
* related changes to the project team guide to add review guidelines:
  https://review.openstack.org/#/c/574888/ and
  https://docs.openstack.org/project-team-guide/review-the-openstack-way.html
* The consensus seemed to be that we should go ahead and update past
  goal documents when projects complete them, so I approved the patch to
  add details to the python 3.5 goal for Kolla:
  https://review.openstack.org/#/c/557863

Office hour logs from last week:

* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-12-09.02.html
* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-13-01.00.html
* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-14-15.01.html

A few folks expressed concern that using the meeting bot to record the
office hours made them more like a meeting. It would be useful to have
some feedback from the community about whether having the logs separate
is helfpul, or if linking to the timestamp in the regular channel logs
would be sufficient.


== Ongoing Discussions ==

I filled out the remaining liaison assignments for TC members to be
responsible for reaching out to project teams. Our goal is to check in
with each team between now and the PTG, and record notes in the wiki.
Information about several teams is already available there.

* http://lists.openstack.org/pipermail/openstack-dev/2018-June/131507.html
* https://wiki.openstack.org/wiki/OpenStack_health_tracker

The resolution layout out the Python 2 deprecation timeline and deadline
for supporting Python 3 is approved and I have started writing up a
"python 3 first" goal to be considered for Stein.

* https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
* https://review.openstack.org/#/c/575933/

Zane's proposal to clarify diversity requirements for new projects is
receiving some discussion.

* https://review.openstack.org/567944

Zane has started a draft of a technical vision for OpenStack

* https://etherpad.openstack.org/p/tech-vision-2018

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

Jeremy's proposal to add a "Castellan-compatible key store" to the base
services list seems to have good support but has not yet reached
majority. TC members, please review.

* https://review.openstack.org/572656

Ian's update to the PTI for documentation translation and PDF generation
has some review feedback and needs to be updated.

* https://review.openstack.org/572559

== 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.

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-dev at lists.openstack.org
and use the subject tag "[tc]" to bring it to the attention of TC
members.