Difference between revisions of "Technical Committee Tracker"
(→Clarifying the terms of service for hosted projects: this is being worked out with the infra team as part of the winterscale changes) |
(→Reviewing TC Office Hour Times and Locations) |
||
Line 70: | Line 70: | ||
During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible. | During the retrospective at the Rocky Forum we talked about changing our office hour times or using different tools to make them more accessible. | ||
+ | |||
+ | 9-9-2018 - chair to raise this question with the TC after the election completes | ||
References | References |
Revision as of 03:34, 10 September 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/09/10
Contents
- 1 Project team changes
- 2 Documentation Changes
- 3 Other Initiatives
- 3.1 Starting work on constellations
- 3.2 Correction to TC member election section of bylaws
- 3.3 Technical Vision for OpenStack
- 3.4 tags indicating the upgrade support in deployment tools
- 3.5 Reviewing the TC Vision
- 3.6 Reviewing TC Office Hour Times and Locations
- 3.7 Actively Monitoring Teams
- 3.8 Status of Electorate
- 3.9 Improving the help-wanted list
- 3.10 project infrastructure governance proposal
- 3.11 finding help for the unified CLI team
- 3.12 Update PTI around project doc translation and PDF
- 3.13 Project team guide: add "technical design tenets" chapter
- 3.14 Clarifying Requirements for PTL Contact Details
- 4 Tracking OpenStack team health
- 5 Recently completed things
Project team changes
Documentation Changes
Other Initiatives
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
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…"
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
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.
9-9-2018 - chair to raise this question with the TC after the election completes
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:
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:
- https://review.openstack.org/#/c/589696/ (abandoned)
- https://review.openstack.org/#/c/590082/ (fills in missing nicks with "None supplied")
Tracking OpenStack team health
See OpenStack_health_tracker for liaison assignment and status updates.