Jump to: navigation, search

Difference between revisions of "Technical Committee Tracker"

(SIGs)
 
(95 intermediate revisions by 11 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. Since Xena release cycle we started to track the per release items in etherpad. In start of the every release cycle, the OpenStack Technical Committee will prepare that release tracker which can include the backlogs from previous release if any item is not finished and worth to continue.
  
Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].
+
We hold the [https://governance.openstack.org/tc/#meeting-office-hour  weekly meeting] on Thursday at 1500 UTC in #openstack-tc IRC channel.
  
'''Status last updated: {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY2}}'''
+
Other tasks can be found in [https://storyboard.openstack.org/#!/project/923 the storyboard project].
  
== Project team changes ==
+
* [https://etherpad.opendev.org/p/tc-xena-tracker  Xena Release Cycle Tracker]
* 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" [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 ===
 
Drivers: mugsie, dhellmann
 
 
 
Status: Under discussion
 
 
 
References
 
* [https://review.openstack.org/561922 PTI documentation change]
 
* [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline]
 
* [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]
 
 
 
=== Starting work on constellations ===
 
 
 
Drivers:
 
 
 
Status: Under discussion
 
 
 
References
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html openstack-dev mailing list post]
 
* [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]
 
 
 
=== 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 ===
 
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 [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 ===
 
Drivers: mnaser, EmilienM
 
 
 
Status: [https://storyboard.openstack.org/#!/story/2002123 In progress]
 
 
 
References
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130913.html ML thread post-summit discussions]
 
* [https://review.openstack.org/#/c/569562/ 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
 
* [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
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130807.html openstack-dev mailing list thread raising the topic]
 
 
 
=== 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
 
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session]
 
 
 
=== 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
 
* [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21738/s-release-goals Rocky Forum session]
 
 
 
=== Anti-nitpicking Cultural Change ===
 
Drivers: TheJulia, ttx
 
 
 
Status: In progress
 
 
 
References
 
* [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130802.html openstack-dev mailing list thread]
 
 
 
=== 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 ===
 
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
 
* [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes]
 
 
 
=== Reviewing the TC Vision ===
 
Drivers: ttx, EmilienM, fungi
 
 
 
Status: [https://storyboard.openstack.org/#!/story/2002132 In progress]
 
 
 
References
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
 
 
=== 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
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
 
 
=== 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
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
 
 
=== 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
 
* [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
 
 
 
=== 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
 
* [https://etherpad.openstack.org/p/job-description-template Sample Job description template]
 
 
 
=== 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
 
* http://lists.openstack.org/pipermail/openstack-dev/2018-May/130896.html
 
 
 
=== 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, [[OpenStack_SIGs|SIGs]], or [[UserCommittee#Working_Groups_and_Teams|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 ===
 
 
 
* API
 
** TC members:
 
* FEMDC
 
** TC members:
 
* First Contact
 
** TC members: fungi
 
* K8s
 
** TC members: dims
 
* Resource Management
 
** TC members:
 
* Scientific
 
** TC members:
 
* Security
 
** TC members: fungi
 
* Self-healing
 
** TC members:
 
* Upgrade
 
** TC members:
 
 
 
=== Working Groups ===
 
 
 
* App Dev Enablement
 
** TC members:
 
* Enterprise
 
** TC members:
 
* Fault Genes
 
** TC members:
 
* [[InteropWG|Interop]]
 
** TC members:
 
* LCOO
 
** TC members:
 
* Large Deployment
 
** TC members:
 
* Massively Distributed Clouds
 
** TC members:
 
* Ops Tags
 
** TC members:
 
* Operators Telecom/NFV
 
** TC members:
 
* Product
 
** TC members:
 
 
 
=== Project Teams ===
 
 
 
* Barbican
 
** TC members:  fungi
 
* Blazar
 
** TC members:
 
* Chef Openstack
 
** TC members:
 
* Cinder
 
** TC members:
 
* 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:
 
* Heat
 
** TC members:
 
* Horizon
 
** TC members:
 
* I18n
 
** TC members:
 
* Infrastructure
 
** TC members:  fungi
 
* Ironic
 
** TC members:
 
* Karbor
 
** TC members:
 
* Keystone
 
** TC members:  fungi
 
* Kolla
 
** TC members:
 
* Kuryr
 
** TC members:
 
* Loci
 
** TC members:
 
* Magnum
 
** TC members:
 
* Manila
 
** TC members:
 
* 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:
 
* 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
 
* 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
 
* Storlets
 
** TC members:
 
* Swift
 
** TC members:
 
* 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:
 

Latest revision as of 21:05, 14 June 2021

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. Since Xena release cycle we started to track the per release items in etherpad. In start of the every release cycle, the OpenStack Technical Committee will prepare that release tracker which can include the backlogs from previous release if any item is not finished and worth to continue.

We hold the weekly meeting on Thursday at 1500 UTC in #openstack-tc IRC channel.

Other tasks can be found in the storyboard project.