Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
 
(40 intermediate revisions by 10 users not shown)
Line 10: Line 10:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: 6 Jun 2019
+
* Date: 16 January 2020
* Chair: mnaser (or asettle if mnaser has a breakdown)
+
* Chair: evrardjp
* Agenda will be published on the openstack-discuss mailing list before the meeting
+
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 
==== Agenda Suggestions ====
 
==== Agenda Suggestions ====
  
All items are from the PTG etherpad at [1]
+
* Follow up on past action items
 +
** ricolin: (in March 2020): Report on whether guidelines worked.
 +
** ttx: Report on large scale sig -- how does this fly and how are the action items.
 +
** mnaser: report on infra liaison and static hosting
 +
** ttx: report about the vision reflection update, that should be started in January
 +
** jungleboyj: report on the blog post for the analysis of the survey
 +
** ttx (report in Feb 2020): Report on tc/uc merge
 +
** mnaser: report on stable branch policy work.
  
* Changes to the health check process. The suggestion was to remove the formality of "health checks" and focus on TC members being liaisons to projects in an effort to help manage a project's health (if required). We need to assign TC members to teams on the project team page. fungi offered to update the wiki, and asettle offered to update the ML on this change once the wiki was updated. See more action items on line 62 of the etherpad.
+
* New initiatives and/or report on previous initiatives
 +
** gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
 +
*** anyone to help gmann?
 +
** ...
  
* Evolution of the help-most-needed list - this was discussed and decided to become an uncapped list, adding docs surrounding annual re-submission for items. We will go through the action items on this list (line 84 of the etherpad). Business cases requiring updates.
 
  
* Goal selection is changing. The way goals are being selected for the upcoming release will change. For Train, we will work on socialising the idea of proposing goals that are OpenStack-wide, but not tech-heavy. The new goal selection process splits the goals into "goal" and "implementation". Further details at the meeting. See line 101 of the etherpad for action items.
+
* addendums
 
 
* Pop-up teams have been officially recognised and implemented into governance thanks to ttx. Please review his patch here [2]
 
 
 
* SIG governance is being defined (ricolin and asettle). See line 137 for action items. Will detail further at meeting.
 
 
 
* Python 3 check in. Finalising the migration (mugsie)
 
 
 
* Leaderless projects are becoming a concern - action items were on line 185 of the etherpad. Suggestions include reworking the documentation around the current role of the PTL and providing tips on how to "be a better PTL" and offering shadowing and mentoring for potential candidates. This all needs to be socialised further.
 
 
 
* Kickstarting innovation in Openstack - Zane proposed a zany (har har har) suggestion regarding a new multi-tenant cloud with ironic/neutron/optionally cinder/keytstone/octavia (vision will be completed with k8s on top of OpenStack). Suggestion was for new whitepaper written by zaneb and mnaser.
 
 
 
* Deleting all the things! [3] See line 234 for action items (mugsie).
 
 
 
[1] https://etherpad.openstack.org/p/tc-train-ptg
 
 
 
[2] https://review.opendev.org/#/c/661356/
 
 
 
[3] https://memegenerator.net/img/instances/14634311.jpg
 
 
 
 
 
* Forum session planning for the next summit as this one was done rather hastily and we missed a few things (such as a goals session). See action items on line 243 of the PTG etherpad [1]
 
 
 
* Socialising successbot and thanksbot. Get to it, team!
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====

Latest revision as of 15:37, 5 December 2019


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/ .

In order to include as many people as possible in the discussion, the Technical Committee relies on asynchronous communications as much as possible. We propose and vote on changes through the openstack/governance repository. Large-impact changes are discussed on the openstack-discuss mailing-list. We track current initiatives on the Technical_Committee_Tracker.

We hold office hours at various times during the week on the #openstack-tc IRC channel. We meet formally on the first Thursday of each month in #openstack-tc at 1400 UTC.


Next Meeting

  • Date: 16 January 2020
  • Chair: evrardjp
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: (in March 2020): Report on whether guidelines worked.
    • ttx: Report on large scale sig -- how does this fly and how are the action items.
    • mnaser: report on infra liaison and static hosting
    • ttx: report about the vision reflection update, that should be started in January
    • jungleboyj: report on the blog post for the analysis of the survey
    • ttx (report in Feb 2020): Report on tc/uc merge
    • mnaser: report on stable branch policy work.
  • New initiatives and/or report on previous initiatives
    • gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
      • anyone to help gmann?
    • ...


  • addendums

Apologies for Absence

Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc