Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda Suggestions)
(Next Meeting)
(13 intermediate revisions by 4 users not shown)
Line 10: Line 10:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: 10 October 2019
+
* Date: 16 January 2020
* Chair: asettle
+
* Chair: evrardjp
 
* Agenda to be published on the openstack-discuss mailing list before the meeting
 
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
Line 17: Line 17:
  
 
* Follow up on past action items
 
* Follow up on past action items
** ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
+
** ricolin: (in March 2020): Report on whether guidelines worked.  
** ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
+
** ttx: Report on large scale sig -- how does this fly and how are the action items.
** Release Naming - Results of the TC poll - Next action
+
** 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
 
* New initiatives and/or report on previous initiatives
** Help gmann on the community goals following our new goal process
+
** gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
** define goal select process schedule
+
*** anyone to help gmann?
This is different discussion to select goals. We need to make sure we can have a schedule for cycles to follow. So we know when exactly to ask for goal idea, ask for champion, start +1 cycle goal select process, and start +2 cycle select process.
+
** ...
** Maintain issue with Telemetery
+
 
** mugsie: to sync with dhellmann or release-team to find the code for the proposal bot
+
 
** jroll - ttx: Feedback from the forum selection committee -- Follow up on https://etherpad.openstack.org/p/PVG-TC-brainstorming -- Final accepted list?
+
* addendums
** mnaser: sync up with swift team on python3 migration
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
evrardjp - Travelling
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

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