Difference between revisions of "Technical Committee Tracker"
(→Liaisons) |
(→Working Groups) |
||
Line 292: | Line 292: | ||
=== Working Groups === | === Working Groups === | ||
− | + | {| class="wikitable" | |
− | + | |- | |
− | + | ! Group !! TC members | |
− | + | |- | |
− | + | | App Dev Enablement | |
− | + | || | |
− | + | |- | |
− | + | | Enterprise | |
− | + | || | |
− | + | |- | |
− | + | | Fault Genes | |
− | + | || | |
− | + | |- | |
− | + | | [[InteropWG|Interop]] | |
− | + | || dims | |
− | + | |- | |
− | + | | LCOO | |
− | + | || | |
− | + | |- | |
− | + | | Large Deployment | |
+ | || | ||
+ | |- | ||
+ | | Massively Distributed Clouds | ||
+ | || | ||
+ | |- | ||
+ | | Ops Tags | ||
+ | || smcginnis | ||
+ | |- | ||
+ | | Operators Telecom/NFV | ||
+ | || smcginnis | ||
+ | |- | ||
+ | | Product | ||
+ | || | ||
+ | |} | ||
=== Project Teams === | === Project Teams === |
Revision as of 18:51, 7 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/07
Contents
- 1 Project team changes
- 2 Other Initiatives
- 2.1 Adjutant official project status
- 2.2 Allow projects to drop py27 support in the PTI
- 2.3 Starting work on constellations
- 2.4 Clarify new project requirements for affiliation diversity
- 2.5 Adding a key manager to base services
- 2.6 Improving the visibility of status updates and announcements
- 2.7 Correction to TC member election section of bylaws
- 2.8 How do we track updates to old goals for new projects?
- 2.9 Ownership and publishing for the operations guide
- 2.10 StarlingX
- 2.11 Murano Team Status
- 2.12 Organizational diversity tags
- 2.13 Clarifying the terms of service for hosted projects
- 2.14 Technical Vision for OpenStack
- 2.15 Stein Series Goals
- 2.16 Anti-nitpicking Cultural Change
- 2.17 Trove Project Health
- 2.18 tags indicating the upgrade support in deployment tools
- 2.19 Reviewing the TC Vision
- 2.20 Reviewing TC Office Hour Times and Locations
- 2.21 Actively Monitoring Teams
- 2.22 Status of Electorate
- 2.23 Improving the help-wanted list
- 2.24 project infrastructure governance proposal
- 2.25 finding help for the unified CLI team
- 3 Liaisons
Project team changes
- PowerVMStackers following stable policy https://review.openstack.org/#/c/562591/
- Status: Approved
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
- PTI documentation change
- governance resolution describing the deprecation timeline
- Rocky Forum session notes
- summary of Rocky Forum discussion
Starting work on constellations
Drivers:
Status: Under discussion
References
- openstack-dev mailing list post
- new git repository to hold the docs
- first draft of scientific computing constellation
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
- https://etherpad.openstack.org/p/BOS-forum-key-management
- ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
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
- See the Kolla Python 3.5 update for example.
- 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
Drivers: mnaser, EmilienM
Status: In progress
References
- ML thread following up from summit
- ML thread post-summit discussions
- project-config change to import some of the repositories
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
- Missing features in OpenStack for public clouds forum session notes
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
SIGs
Group | TC members |
---|---|
API | |
FEMDC | |
First Contact | fungi |
K8s | dims |
Resource Management | |
Scientific | |
Security | fungi |
Self-healing | |
Upgrade |
Working Groups
Group | TC members |
---|---|
App Dev Enablement | |
Enterprise | |
Fault Genes | |
Interop | dims |
LCOO | |
Large Deployment | |
Massively Distributed Clouds | |
Ops Tags | smcginnis |
Operators Telecom/NFV | smcginnis |
Product |
Project Teams
- Barbican
- TC members: fungi
- Blazar
- TC members:
- Chef Openstack
- TC members:
- Cinder
- TC members: smcginnis
- Cloudkitty
- TC members:
- Congress
- TC members:
- Cyborg
- TC members:
- Designate
- TC members:
- Documentation
- TC members:
- Dragonflow
- TC members:
- Ec2-Api
- TC members:
- Freezer
- TC members:
- Glance
- TC members: smcginnis
- Heat
- TC members:
- Horizon
- TC members:
- I18n
- TC members:
- Infrastructure
- TC members: fungi
- Ironic
- TC members:
- Karbor
- TC members:
- Keystone
- TC members: fungi,cmurphy
- Kolla
- TC members:
- Kuryr
- TC members:
- Loci
- TC members:
- Magnum
- TC members:
- Manila
- TC members: smcginnis
- Masakari
- TC members:
- Mistral
- TC members:
- Monasca
- TC members:
- Murano
- TC members:
- Neutron
- TC members:
- Nova
- TC members:
- Octavia
- TC members:
- Openstack Charms
- TC members:
- Openstack-Helm
- TC members:
- Openstackansible
- TC members:
- Openstackclient
- TC members: dhellmann
- Openstacksdk
- TC members:
- Oslo
- TC members: dhellmann
- Packaging-Rpm
- TC members: cmurphy
- Powervmstackers
- TC members:
- Puppet Openstack
- TC members:
- Qinling
- TC members:
- Quality Assurance
- TC members:
- Rally
- TC members:
- Refstack
- TC members: fungi
- Release Management
- TC members: dhellmann, smcginnis
- Requirements
- TC members: fungi, dhellmann
- Sahara
- TC members:
- Searchlight
- TC members:
- Security
- TC members: fungi
- Senlin
- TC members:
- Solum
- TC members:
- Stable Branch Maintenance
- TC members: fungi, smcginnis
- Storlets
- TC members:
- Swift
- TC members: smcginnis
- Tacker
- TC members:
- Telemetry
- TC members:
- Tricircle
- TC members:
- Tripleo
- TC members:
- Trove
- TC members:
- Vitrage
- TC members:
- Watcher
- TC members:
- Winstackers
- TC members:
- Zaqar
- TC members:
- Zun
- TC members: