Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

(SIGs: add cdent to resource management, already a member)
(SIGs)
Line 275: Line 275:
 
|-
 
|-
 
| Meta
 
| Meta
||  
+
|| dhellmann
 
|-
 
|-
 
| Resource Management
 
| Resource Management

Revision as of 19:40, 8 June 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.

Other tasks can be found in the storyboard project.

Status last updated: 2018/06/08

Project team changes

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

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

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

How do we track updates to old goals for new projects?

Drivers: dhellmann

Status: In progress

References

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

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

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

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.

Liaisons

This section of the tracker lists the TC members attached as liaisons to each of the project teams, SIGs, or 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.

Liaisons should monitor their groups by:

  • reading meeting logs or participating in meetings
  • 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

Group TC members
API mugsie
First Contact fungi
K8s dims
Meta dhellmann
Resource Management cdent
Scientific
Security fungi
Self-healing zaneb
Upgrade

Working Groups

Group TC members
App Dev Enablement zaneb
Diversity fungi
Enterprise
Fault Genes
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

Group TC members
Barbican fungi, ttx
Blazar
Chef Openstack
Cinder smcginnis
Cloudkitty ttx
Congress
Cyborg ttx
Designate
Documentation dhellmann
Dragonflow
Ec2-Api
Freezer ttx, mugsie
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