|
|
(43 intermediate revisions by 6 users not shown) |
Line 14: |
Line 14: |
| == Other Initiatives == | | == Other Initiatives == |
| | | |
− | === Adjutant official project status === | + | === Help most needed list evolution === |
− | Drivers: zaneb | + | Drivers: ttx |
− | | |
− | 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]
| + | Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002252.html mailing-list] |
| | | |
− | References
| + | Next step: Forum session |
− | * [https://review.openstack.org/553643 project team application]
| |
| | | |
− | === Allow projects to drop py27 support in the PTI ===
| + | Asking for help was not very successful, partially due to how intimidating it is for new contributors to join. Maybe proposing mentoring if you offer time is a more positive way to look at it. |
− | Drivers: mugsie, dhellmann
| |
| | | |
− | Status: Under discussion
| + | === Facilitating cross-project work / Formalizing pop-up teams === |
− | | + | Drivers: ttx |
− | References
| |
− | * [https://review.openstack.org/561922 PTI documentation change]
| |
− | * [https://review.openstack.org/#/c/571011/ governance resolution describing the deprecation timeline] APPROVED
| |
− | * [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]
| |
− | * [https://review.openstack.org/#/c/575933/ python 3 as default goal]
| |
− | | |
− | === 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: Discussing going beyond "castellan-compatible"
| |
− | | |
− | References
| |
− | * https://etherpad.openstack.org/p/BOS-forum-key-management
| |
− | * ML thread: http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html
| |
− | * https://review.openstack.org/572656 castellan-compatible key store - APPROVED
| |
− | | |
− | === 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…"
| |
− | | |
− | === StarlingX ===
| |
− | Drivers: mnaser, EmilienM
| |
| | | |
− | Status: [https://storyboard.openstack.org/#!/story/2002123 In progress] | + | Status: under discussion on the [http://lists.openstack.org/pipermail/openstack-discuss/2019-January/002251.html mailing-list] |
| | | |
− | References
| + | Next step: Forum session |
− | * [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 ===
| + | Cross-project work is still difficult. Maybe formalizing the concept of pop-up teams a bit more, with clear scope and disband criteria (under the model of [https://github.com/kubernetes/community/blob/master/committee-steering/governance/wg-governance.md Kubernetes working groups]) would help. |
− | 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]
| |
− | * removing the tags: https://review.openstack.org/#/c/579870/
| |
− | * team "fragility" stats script: https://review.openstack.org/#/c/579142/
| |
− | | |
− | === 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 === | | === Technical Vision for OpenStack === |
− | Drivers: zaneb, ttx, cdent | + | Drivers: zaneb, cdent |
| | | |
− | Status: Early | + | 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.
| + | The initial [https://governance.openstack.org/tc/reference/technical-vision.html vision] has been created. The agreed next step (to be done by cdent and TheJulia) is to publicize it and request that projects self-evaluate themselves against the vision. |
| | | |
| References | | References |
| * [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session] | | * [https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21739/official-projects-and-the-boundary-of-what-is-openstack Rocky Forum session] |
| * https://etherpad.openstack.org/p/tech-vision-2018 | | * https://etherpad.openstack.org/p/tech-vision-2018 |
| + | * [https://review.openstack.org/592205 Document review] |
| | | |
− | === Stein Series Goals === | + | === Tags indicating the upgrade support in deployment tools === |
− | 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]
| |
− | * [https://review.openstack.org/#/c/570940/ principle about valuing peer review] APPROVED
| |
− | | |
− | === Trove Project Health ===
| |
− | Drivers: ttx, theJulia, mugsie?
| |
− | | |
− | Status: In progress
| |
− | | |
− | During the public cloud issues session at the Rocky Forum someone in the room raised the question of whether Trove is still actively maintained.
| |
− | | |
− | ttx looked up Trove as part of the "liaison" duties -- at first glance it appears to be alive and kicking. Will report more when I know more.
| |
− | | |
− | 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 | | Drivers: ttx |
| | | |
Line 168: |
Line 54: |
| * [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes] | | * [https://etherpad.openstack.org/p/YVR-forum-fast-forward-upgrades Rocky Forum session notes] |
| | | |
− | === Reviewing the TC Vision === | + | === Do a better job at driving larger technical goals === |
− | Drivers: ttx, EmilienM, fungi | + | Drivers: ttx, TheJulia, cdent |
| | | |
− | Status: [https://storyboard.openstack.org/#!/story/2002132 In progress] | + | Status: |
| + | Documenting the role of the TC revealed the need for the TC to do a better job at painting larger technical goals for the OpenStack community, beyond release goals. |
| | | |
− | References
| + | Next step: Forum session |
− | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
| |
| | | |
− | === Reviewing TC Office Hour Times and Locations === | + | === Clarifying Requirements for PTL Contact Details === |
− | 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: 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
| |
− | * [https://etherpad.openstack.org/p/YVR-tc-retrospective TC Retrospective Notes from Rocky Forum]
| |
− | * [[OpenStack_health_tracker]]
| |
− |
| |
− | === Status of Electorate ===
| |
| Drivers: | | Drivers: |
| | | |
− | Status: New
| + | 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. |
− | | |
− | 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: Sean, Graham, Dims, and Julia
| |
| | | |
− | Board support: Allison Randal, Alan Clark, Prakash Ramchandran, Chris Price, and Johan Christenson
| + | 2018-09-09 - need to figure out how to ask PTLs for a primary means of contact without dictating a specific means and without opening ourselves up to having to sign on to every new chat tool |
| | | |
| Status: New | | 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.
| |
− |
| |
− | === Update PTI around project doc translation and PDF ===
| |
− | Drivers:
| |
− |
| |
− | Status: Under discussion
| |
| | | |
| References: | | References: |
− | * https://review.openstack.org/572559
| |
| | | |
− | === Project team guide: add "technical design tenets" chapter ===
| + | * https://review.openstack.org/#/c/589696/ (abandoned) |
| + | * https://review.openstack.org/#/c/590082/ (fills in missing nicks with "None supplied") |
| | | |
− | Drivers: ttx
| + | == Tracking OpenStack team health == |
− | | + | See [[OpenStack_health_tracker]] for liaison assignment and status updates. |
− | 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:
| |
− | https://storyboard.openstack.org/#!/story/2002611
| |
− | | |
− | === Scheduling PTL & TC elections for Stein ===
| |
− | | |
− | Drivers: cmurphy
| |
− | | |
− | 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:
| |
| | | |
− | * https://governance.openstack.org/tc/reference/charter.html#election-for-ptl-seats
| |
− | * https://governance.openstack.org/tc/reference/charter.html#election-for-tc-seats
| |
− | * election setup: https://review.openstack.org/#/c/582109/
| |
| | | |
− | == Tracking OpenStack team health == | + | == Recently completed things == |
− | See [[OpenStack_health_tracker]] for liaison assignment and status updates.
| |
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.
Asking for help was not very successful, partially due to how intimidating it is for new contributors to join. Maybe proposing mentoring if you offer time is a more positive way to look at it.
Cross-project work is still difficult. Maybe formalizing the concept of pop-up teams a bit more, with clear scope and disband criteria (under the model of Kubernetes working groups) would help.
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.
Status:
Documenting the role of the TC revealed the need for the TC to do a better job at painting larger technical goals for the OpenStack community, beyond release goals.
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.
2018-09-09 - need to figure out how to ask PTLs for a primary means of contact without dictating a specific means and without opening ourselves up to having to sign on to every new chat tool