[openstack-dev] [tc] Technical Committee Update for 3 July

Doug Hellmann doug at doughellmann.com
Tue Jul 3 18:16:18 UTC 2018


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

Approved changes:

* add a note about tracking cycle goals after a cycle ends:
  https://review.openstack.org/#/c/577149/

Office hour logs from last week:

* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-27-01.00.html
* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-06-28-15.00.html
* http://eavesdrop.openstack.org/meetings/tc/2018/tc.2018-07-03-09.01.html

In the absence of any feedback about using the meeting bot to record the
office hours, we will continue to do so, for now.

== Ongoing Discussions ==

The Adjutant team application is still under discussion.

* https://review.openstack.org/553643 project team application

Discussions about affiliation diversity continue in two directions.
Zane's proposal for requirements for new project teams has stalled a
bit. The work Thierry and Mohammed have done on the diversity tags has
brought a new statistics script and a proposal to drop the use of the
tags in favor of folding the diversity information into the more general
health checks we are doing. Thierry has updated the health tracker page
with information about all of the teams based on the most recent run of
the scripts.

* Zane's proposal for requirements for new projects:
* https://review.openstack.org/#/c/567944/
* Thierry's proposal to drop the tags:
* https://review.openstack.org/#/c/579870/
* Team "fragility" scripts: https://review.openstack.org/#/c/579142/

Thierry proposed changes to the Project Team Guide to include a
technical guidance section.

* https://review.openstack.org/#/c/578070/1

Chris and Thierry have been discussing a technical vision for OpenStack.

* https://etherpad.openstack.org/p/tech-vision-2018
* http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-06-26.log.html#t2018-06-26T09:09:57

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

Please vote on the Adjutant team application.
https://review.openstack.org/553643

Project team "health check" interviews continue. Our goal is to check in
with each team between now and the PTG, and record notes in the wiki.

* https://wiki.openstack.org/wiki/OpenStack_health_tracker

Remember that we agreed to send status updates on initiatives separately
to openstack-dev every two weeks. If you are working on something for
which there has not been an update in a couple of weeks, please consider
summarizing the status.

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




More information about the OpenStack-dev mailing list