Difference between revisions of "Technical Committee Tracker"

Revision as of 17:42, 30 May 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.

Status last updated: 2018/05/30

Project team changes

Adjutant official project status [1]
- 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]
Import ansible-role-tripleo-modify-image [4]
- Status: Approved

Other

Allow projects to drop py27 support in the PTI [5]
- Drivers: mugsie
- Status: Under discussion
Starting work on constellations
- Drivers:
- Status: Under discussion [6]
Update the requirements for affiliation diversity for new projects [7]
- Drivers: zaneb
- Status: Under discussion
Clarify new project requirements for affiliation diversity [8]
- Drivers: zaneb
- Status: Under discussion
Include the rationale for tracking base services [9]
- Drivers: fungi
- Status: Approved
Note that the old incubation/graduation process is obsolete [10]
Drivers: zaneb
- Status: Approved
Adding a key manager to base services
- Drivers: fungi
- 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
  - Investigating mailman 3, blogging, and Matrix, among other solutions.
Correction to TC member election section of bylaws
- Drivers: fungi, dhellmann
- Status: 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
- See the Kolla Python 3.5 update for example.
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 discussion
- References
  - ML thread following up from summit
  - project-config change to import some of the repositories

@@ Line 15: / Line 15: @@
 ==== Other ====
 * Allow projects to drop py27 support in the PTI [https://review.openstack.org/561922]
+** Drivers: mugsie
 ** Status: Under discussion
-* Join the leadership meeting at the summit in Vancouver
-** [[Governance/Foundation/20May2018BoardMeeting]]
 * Starting work on constellations
+** Drivers:
 ** Status: Under discussion [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130068.html]
 * Update the requirements for affiliation diversity for new projects [https://review.openstack.org/#/c/567944/]
+** Drivers: zaneb
 ** Status: Under discussion
 * Clarify new project requirements for affiliation diversity [https://review.openstack.org/567944]
+** Drivers: zaneb
 ** Status: Under discussion
 * Include the rationale for tracking base services [https://review.openstack.org/#/c/568941/]
+** Drivers: fungi
 ** Status: Approved
 * Note that the old incubation/graduation process is obsolete [https://review.openstack.org/569164]
+* Drivers: zaneb
 ** Status: Approved
+* Adding a key manager to base services
+** Drivers: fungi
+** 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
+*** Investigating mailman 3, blogging, and Matrix, among other solutions.
+* Correction to TC member election section of bylaws
+** Drivers: fungi, dhellmann
+** Status: 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
+** See the [https://review.openstack.org/#/c/557863/ Kolla Python 3.5 update] for example.
+* 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 discussion
+** References
+*** [http://lists.openstack.org/pipermail/openstack-dev/2018-May/130715.html ML thread following up from summit]
+*** [https://review.openstack.org/#/c/569562/ project-config change to import some of the repositories]