Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

(SIGs: add cdent to resource management, already a member)
(Link to Technical Vision review)
(35 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
 
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
  
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing.
+
This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. Conversation starters for the office hours are [https://etherpad.openstack.org/p/tc-office-hour-conversation-starters here].
  
Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].
+
Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].  
  
 
'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''
 
'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''
  
 
== Project team changes ==
 
== Project team changes ==
* PowerVMStackers following stable policy https://review.openstack.org/#/c/562591/
 
** Status: Approved
 
* Add openstackclient to Chef OpenStack https://review.openstack.org/#/c/571504/
 
** Status: Approved
 
  
== Other Initiatives ==
+
== Documentation Changes ==
  
=== Adjutant official project status ===
 
Drivers: zaneb
 
  
Status: Under discussion
+
== Other Initiatives ==
 
 
The Adjutant team will not be present at the forum, but we will discuss our approach to reviewing team applications in general during the TC session about project "boundaries" [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack] and Adjutant in particular on Thursday afternoon [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21752/adjutant-official-project-status]
 
 
 
References
 
* [https://review.openstack.org/553643 project team application]
 
  
 
=== Allow projects to drop py27 support in the PTI ===
 
=== Allow projects to drop py27 support in the PTI ===
Line 32: Line 21:
 
References
 
References
 
* [https://review.openstack.org/561922 PTI documentation change]
 
* [https://review.openstack.org/561922 PTI documentation change]
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline]
+
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline] APPROVED
 
* [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes]
 
* [https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline Rocky Forum session notes]
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130824.html summary of Rocky Forum discussion]
 +
* [https://review.openstack.org/#/c/575933/ python 3 as default goal]
  
 
=== Starting work on constellations ===
 
=== Starting work on constellations ===
Line 46: Line 36:
 
* [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
 
* [http://git.openstack.org/cgit/openstack/constellations/ new git repository to hold the docs]
 
* [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation]
 
* [https://review.openstack.org/#/c/565466/ first draft of scientific computing constellation]
 
=== Clarify new project requirements for affiliation diversity ===
 
Drivers: zaneb
 
 
Status: Under discussion
 
 
References
 
* https://review.openstack.org/567944
 
  
 
=== Adding a key manager to base services ===
 
=== Adding a key manager to base services ===
 
Drivers: fungi
 
Drivers: fungi
  
Status: In progress
+
Status: Discussing going beyond "castellan-compatible"
  
 
References
 
References
 
* https://etherpad.openstack.org/p/BOS-forum-key-management
 
* https://etherpad.openstack.org/p/BOS-forum-key-management
 
* ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
 
* ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
 +
* https://review.openstack.org/572656 castellan-compatible key store - APPROVED
  
 
=== Improving the visibility of status updates and announcements ===
 
=== Improving the visibility of status updates and announcements ===
Line 79: Line 62:
  
 
Section [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"
 
Section [https://www.openstack.org/legal/technical-committee-member-policy/ 3.b.i] reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"
 
=== How do we track updates to old goals for new projects? ===
 
Drivers: dhellmann
 
 
Status: In progress
 
 
References
 
* See the [https://review.openstack.org/#/c/557863/ Kolla Python 3.5 update] for example.
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130236.html openstack-dev mailing list thread]
 
 
=== Ownership and publishing for the operations guide ===
 
Drivers: dhellmann
 
 
Status: Resolved, they will start a SIG to own the repository for the guide so it can be published to docs.openstack.org.
 
 
References
 
* Wednesday, May 23, 2018 - session at Vancouver summit
 
* http://lists.openstack.org/pipermail/openstack-operators/2018-May/015321.html
 
  
 
=== StarlingX ===
 
=== StarlingX ===
Line 108: Line 73:
 
* [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]
 
* [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]
  
=== Murano Team Status ===
+
=== Clarifying the terms of service for hosted projects ===
Drivers: dhellmann
+
Drivers: zaneb, ttx
 
 
Status: On hold
 
 
 
With ZTE's future at question, a Murano team member contacted me about the future of the project. I am currently waiting for the question to be raised in an email thread.
 
 
 
=== Organizational diversity tags ===
 
Drivers: ttx, mnaser
 
  
 
Status: Under discussion
 
Status: Under discussion
  
References
+
Ties into the OSF project governance discussion at board-level. A strawman should be proposed as a result to the ML soon.
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]
 
 
 
=== Clarifying the terms of service for hosted projects ===
 
Drivers: zaneb
 
 
 
Status: Under discussion
 
  
 
References
 
References
Line 134: Line 86:
 
Drivers: zaneb, ttx, cdent
 
Drivers: zaneb, ttx, cdent
  
Status: Early
+
Status: Under dicussion
  
 
Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.
 
Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.
Line 140: Line 92:
 
References
 
References
 
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]
 
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]
 +
* https://etherpad.openstack.org/p/tech-vision-2018
 +
* [https://review.openstack.org/592205 Document review]
  
 
=== Stein Series Goals ===
 
=== Stein Series Goals ===
Line 154: Line 108:
 
Drivers: TheJulia, ttx
 
Drivers: TheJulia, ttx
  
Status: In progress
+
Status: Done
  
 
References
 
References
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]
 
+
* [https://review.openstack.org/#/c/570940/ principle about valuing peer review] APPROVED
=== Trove Project Health ===
 
Drivers: ttx, theJulia
 
 
 
Status: New
 
 
 
During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
 
 
 
References
 
* [https://etherpad.openstack.org/p/YVR-forum-missing-features-pc Missing features in OpenStack for public clouds] forum session notes
 
  
 
=== tags indicating the upgrade support in deployment tools ===
 
=== tags indicating the upgrade support in deployment tools ===
Line 200: Line 145:
 
Drivers: dhellmann
 
Drivers: dhellmann
  
Status: New
+
Status: In process
  
 
During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.
 
During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.
 
'''Dragonflow''' did not produce a Queens release. Their last release was 4.0.0 on Sept 1, 2017. Should projects that do not prepare releases be considered official? -- dhellmann
 
 
'''Rally''' may be moving out to GitHub? https://github.com/xrally and https://xrally.org -- dhellmann
 
  
 
References
 
References
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 +
* [[OpenStack_health_tracker]]
  
 
=== Status of Electorate ===
 
=== Status of Electorate ===
Line 222: Line 164:
  
 
=== Improving the help-wanted list ===
 
=== Improving the help-wanted list ===
Drivers: dims
+
Drivers: Sean, Graham, Dims, and Julia
 +
 
 +
Board support: Allison Randal, Alan Clark, Prakash Ramchandran, Chris Price, and Johan Christenson
  
 
Status: New
 
Status: New
Line 248: Line 192:
 
During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.
 
During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.
  
== Liaisons ==
+
=== Update PTI around project doc translation and PDF ===
 +
Drivers:
  
This section of the tracker lists the TC members attached as liaisons to each of the project teams, [https://governance.openstack.org/sigs/ SIGs], or [https://governance.openstack.org/uc/ working groups]. The idea is for these liaisons to keep up with the general health of the group, understand any issues they encounter, and help them work with the TC on solutions if necessary. Some TC members may be more active within the group than the basic liaison responsibilities imply, but that is not required.
+
Status: Under discussion
  
Liaisons should monitor their groups by:
+
References:
* reading meeting logs or participating in meetings
+
* https://review.openstack.org/572559
* watching summit "project update" videos
 
* reading relevant messages on the mailing list
 
* talking with the PTL, chair, and other group members
 
* checking contribution rates and review turnaround times
 
  
=== SIGs ===
+
=== Project team guide: add "technical design tenets" chapter ===
  
{| class="wikitable"
+
Drivers: ttx
|-
 
! Group !! TC members
 
|-
 
| API
 
||  mugsie
 
|-
 
| First Contact
 
||  fungi
 
|-
 
| K8s
 
||  dims
 
|-
 
| Meta
 
||
 
|-
 
| Resource Management
 
|| cdent
 
|-
 
| Scientific
 
||
 
|-
 
| Security
 
||  fungi
 
|-
 
| Self-healing
 
|| zaneb
 
|-
 
| Upgrade
 
||
 
|}
 
  
=== Working Groups ===
+
Status: Under discussion
  
{| class="wikitable"
+
We need a place to explain things like base services (external services you can assume will be around and therefore you don't need to reinvent locally) and other basic design tenets.
|-
 
! Group !! TC members
 
|-
 
| App Dev Enablement
 
|| zaneb
 
|-
 
| [[Diversity]]
 
|| fungi
 
|-
 
| Enterprise
 
||
 
|-
 
| Fault Genes
 
||
 
|-
 
| [[InteropWG|Interop]]
 
||  dims, fungi
 
|-
 
| LCOO
 
||
 
|-
 
| Large Deployment
 
||
 
|-
 
| Edge/Massively Distributed Clouds
 
|| ttx
 
|-
 
| Operators Telecom/NFV
 
||  smcginnis
 
|-
 
| Ops Tags
 
||  smcginnis
 
|-
 
| Product
 
||
 
|-
 
| [[ProfessionalCertification]]
 
||
 
|-
 
| Public Cloud
 
||  ttx
 
|}
 
  
=== Project Teams ===
+
References:
 +
https://storyboard.openstack.org/#!/story/2002611
  
{| class="wikitable"
+
=== Scheduling PTL & TC elections for Stein ===
|-
+
 
! Group !! TC members
+
Drivers: cmurphy
|-
+
 
| Barbican
+
Status: Under discussion
||  fungi, ttx
+
 
|-
+
References:
| Blazar
+
 
|| 
+
* https://governance.openstack.org/tc/reference/charter.html#election-for-ptl-seats
|-
+
* https://governance.openstack.org/tc/reference/charter.html#election-for-tc-seats
| Chef Openstack
+
* election setup: https://review.openstack.org/#/c/582109/
|| 
+
* schedule update: https://review.openstack.org/582831
|-
+
 
| Cinder
+
=== Clarifying Requirements for PTL Contact Details ===
||  smcginnis
+
 
|-
+
Drivers:
| Cloudkitty
+
 
||  ttx
+
Monty pointed out that we have a general community expectation that leaders are visible via IRC. That may not always be the case for some corners of our community, however. We need to decide whether we want to require IRC nicks for PTL candidates, whether we want to include other forms of contact for other chat platforms (optionally?), etc. and write a resolution so the election official have clear guidance.
|-
+
 
| Congress
+
Status: New
|| 
+
 
|-
+
References:
| Cyborg
+
 
|| ttx
+
* https://review.openstack.org/#/c/589696/
|-
+
 
| Designate
+
== Tracking OpenStack team health ==
|| 
+
See [[OpenStack_health_tracker]] for liaison assignment and status updates.
|-
+
 
| Documentation
+
 
||  dhellmann
+
== Recently completed things ==
|-
+
 
| Dragonflow
+
=== Organizational diversity tags ===
|| 
+
Drivers: ttx, mnaser
|-
+
 
| Ec2-Api
+
Status: Done
|| 
+
 
|-
+
References
| Freezer
+
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130776.html openstack-dev mailing list thread raising the topic]
||  ttx, mugsie
+
* removing the tags: https://review.openstack.org/#/c/579870/
|-
+
* team "fragility" stats script: https://review.openstack.org/#/c/579142/
| Glance
 
||  smcginnis, mugsie
 
|-
 
| Heat
 
||  zaneb
 
|-
 
| Horizon
 
||  cmurphy
 
|-
 
| I18n
 
|| 
 
|-
 
| Infrastructure
 
||  fungi, mnaser
 
|-
 
| Ironic
 
||  mugsie
 
|-
 
| Karbor
 
||  ttx
 
|-
 
| Keystone
 
||  fungi,cmurphy
 
|-
 
| Kolla
 
|| 
 
|-
 
| Kuryr
 
|| 
 
|-
 
| Loci
 
||
 
|-
 
| Magnum
 
||  mnaser
 
|-
 
| Manila
 
||  smcginnis
 
|-
 
| Masakari
 
|| 
 
|-
 
| Mistral
 
||  zaneb
 
|-
 
| Monasca
 
|| 
 
|-
 
| Murano
 
|| 
 
|-
 
| Neutron
 
||  mugsie
 
|-
 
| Nova
 
||  mnaser
 
|-
 
| Octavia
 
||  mnaser, mugsie
 
|-
 
| Openstack Charms
 
||  ttx
 
|-
 
| Openstack-Helm
 
||  ttx
 
|-
 
| Openstackansible
 
||  mnaser
 
|-
 
| Openstackclient
 
||  dhellmann
 
|-
 
| Openstacksdk
 
|| 
 
|-
 
| Oslo
 
||  dhellmann, mugsie
 
|-
 
| Packaging-Rpm
 
||  cmurphy
 
|-
 
| Powervmstackers
 
|| 
 
|-
 
| Puppet Openstack
 
||  cmurphy
 
|-
 
| Qinling
 
||  zaneb
 
|-
 
| Quality Assurance
 
|| 
 
|-
 
| Rally
 
|| 
 
|-
 
| Refstack
 
||  fungi
 
|-
 
| Release Management
 
||  dhellmann, smcginnis
 
|-
 
| Requirements
 
||  fungi, dhellmann
 
|-
 
| Sahara
 
|| 
 
|-
 
| Searchlight
 
||  mugsie
 
|-
 
| Security
 
||  fungi
 
|-
 
| Senlin
 
||  zaneb
 
|-
 
| Solum
 
|| 
 
|-
 
| Stable Branch Maintenance
 
||  fungi, smcginnis
 
|-
 
| Storlets
 
||  ttx
 
|-
 
| Swift
 
||  smcginnis, mugsie
 
|-
 
| Tacker
 
|| 
 
|-
 
| Telemetry
 
|| 
 
|-
 
| Tricircle
 
|| 
 
|-
 
| Tripleo
 
|| 
 
|-
 
| Trove
 
||  ttx, mugsie
 
|-
 
| Vitrage
 
|| 
 
|-
 
| Watcher
 
|| 
 
|-
 
| Winstackers
 
|| 
 
|-
 
| Zaqar
 
||  zaneb
 
|-
 
| Zun
 
|| zaneb, ttx
 
|}
 

Revision as of 15:24, 16 August 2018

The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack TC governance website at https://governance.openstack.org/tc/ .

This page tracks the various governance changes being proposed and the various initiatives the Technical Committee is pursuing. We hold office hours at various times during the week on the #openstack-tc IRC channel. Conversation starters for the office hours are here.

Other tasks can be found in the storyboard project.

Status last updated: 2018/08/16

Project team changes

Documentation Changes

Other Initiatives

Allow projects to drop py27 support in the PTI

Drivers: mugsie, dhellmann

Status: Under discussion

References

Starting work on constellations

Drivers:

Status: Under discussion

References

Adding a key manager to base services

Drivers: fungi

Status: Discussing going beyond "castellan-compatible"

References

Improving the visibility of status updates and announcements

Drivers: dhellmann, cdent, ttx

Status: In progress

We are investigating mailman 3, blogging, and Matrix, among other solutions.

Correction to TC member election section of bylaws

Drivers: fungi, dhellmann

Status: On hold until the next Foundation vote

This was discussed in the joint leadership meeting in Vancouver. The change requires a member vote, and the Board passed a resolution allowing the Foundation Secretary to propose the bylaws change as part of the next Board election (early 2019). We anticipate other bylaws changes at the same time.

Section 3.b.i reads "An Individual Member is an ATC who has..." but should read "An ATC is an Individual Member who has…"

StarlingX

Drivers: mnaser, EmilienM

Status: In progress

References

Clarifying the terms of service for hosted projects

Drivers: zaneb, ttx

Status: Under discussion

Ties into the OSF project governance discussion at board-level. A strawman should be proposed as a result to the ML soon.

References

Technical Vision for OpenStack

Drivers: zaneb, ttx, cdent

Status: Under dicussion

Zane offered to start creating a "technical vision" for OpenStack to help clarify the boundary for where projects fit into OpenStack and where they may not.

References

Stein Series Goals

Drivers: smcginnis

Status: Early

Sean organized a session at the Rocky Forum to discuss improving our goal selection process and specific goals for Stein.

References

Anti-nitpicking Cultural Change

Drivers: TheJulia, ttx

Status: Done

References

tags indicating the upgrade support in deployment tools

Drivers: ttx

Status: New

During the FFU session at the Rocky Forum, Dan Smith and David Medberry indicated interest in defining tags to describe what upgrade features deployment tools have.

References

Reviewing the TC Vision

Drivers: ttx, EmilienM, fungi

Status: In progress

References

Reviewing TC Office Hour Times and Locations

Drivers: dhellmann

Status: New

During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible.

References

Actively Monitoring Teams

Drivers: dhellmann

Status: In process

During the retrospective at the Rocky Forum we discussed more actively engaging with project teams and SIGs to anticipate issues we can help resolve.

References

Status of Electorate

Drivers:

Status: New

During the retrospective at the Rocky Forum we discussed the status of the TC electorate, and what is perceived as a low level of engagement. This needs a bit more research to compare recent elections so we can understand how things stand, and then we should talk about ways to improve the situation.

References

Improving the help-wanted list

Drivers: Sean, Graham, Dims, and Julia

Board support: Allison Randal, Alan Clark, Prakash Ramchandran, Chris Price, and Johan Christenson

Status: New

During the Board/TC/UC meeting at Vancouver, we came up with an idea on what we can put together a better way to ask platinum/gold and other companies in the eco system for help (crossing traditional job descriptions and volunteer/skill match websites)

References

project infrastructure governance proposal

Drivers: dhellmann

Status: Under discussion

corvus started a discussion about the relationship between the foundation projects and the infrastructure management team as that team shifts from being governed by the TC to being a foundation-wide project.

References

finding help for the unified CLI team

Drivers:

Status: Needs a driver

During the office hours on 7 June we talked about adding OSC to the "help wanted" list. We decided we did not have enough information about what the team needs to write it up yet, so we need someone to gather that information and to propose the addition.

Update PTI around project doc translation and PDF

Drivers:

Status: Under discussion

References:

Project team guide: add "technical design tenets" chapter

Drivers: ttx

Status: Under discussion

We need a place to explain things like base services (external services you can assume will be around and therefore you don't need to reinvent locally) and other basic design tenets.

References: https://storyboard.openstack.org/#!/story/2002611

Scheduling PTL & TC elections for Stein

Drivers: cmurphy

Status: Under discussion

References:

Clarifying Requirements for PTL Contact Details

Drivers:

Monty pointed out that we have a general community expectation that leaders are visible via IRC. That may not always be the case for some corners of our community, however. We need to decide whether we want to require IRC nicks for PTL candidates, whether we want to include other forms of contact for other chat platforms (optionally?), etc. and write a resolution so the election official have clear guidance.

Status: New

References:

Tracking OpenStack team health

See OpenStack_health_tracker for liaison assignment and status updates.


Recently completed things

Organizational diversity tags

Drivers: ttx, mnaser

Status: Done

References