Jump to: navigation, search

Technical Committee Tracker

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/06/20

Project team changes

Documentation Changes

  • add champion section to goal template [1]

Other Initiatives

Adjutant official project status

Drivers: zaneb

Status: Under discussion

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" [2] and Adjutant in particular on Thursday afternoon [3]

References

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

Clarify new project requirements for affiliation diversity

Drivers: zaneb

Status: Under discussion

References

Adding a key manager to base services

Drivers: fungi

Status: Approved

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…"

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

StarlingX

Drivers: mnaser, EmilienM

Status: In progress

References

Murano Team Status

Drivers: dhellmann

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

References

Clarifying the terms of service for hosted projects

Drivers: zaneb

Status: Under discussion

References

Technical Vision for OpenStack

Drivers: zaneb, ttx, cdent

Status: Early

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: In progress

References

Trove Project Health

Drivers: ttx, theJulia, mugsie?

Status: In progress

During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.

ttx looked up Trove as part of the "liaison" duties -- at first glance it appears to be alive and kicking. Will report more when I know more.

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.

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

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: dims

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


Tracking OpenStack team health

See OpenStack_health_tracker for liaison assignment and status updates.