Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

 
(63 intermediate revisions by 13 users not shown)
Line 3: Line 3:
 
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
 
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html 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 [http://git.openstack.org/cgit/openstack/governance openstack/governance repository]. Large-impact changes are discussed on the openstack-dev mailing-list. '''We track current initiatives on the [[Technical_Committee_Tracker]].'''
+
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 [http://git.openstack.org/cgit/openstack/governance 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 [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We meet formally on the first Thursday of each month in #openstack-tc at 1400 UTC.
 
We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We meet formally on the first Thursday of each month in #openstack-tc at 1400 UTC.
Line 10: Line 10:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: 1 Nov 2018
+
* Date: 10 October 2019
* Chair: dhellmann
+
* Chair: asettle
* Agenda: http://lists.openstack.org/pipermail/openstack-dev/2018-October/136146.html
+
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 
==== Agenda Suggestions ====
 
==== Agenda Suggestions ====
  
* dhellmann: Project team health check review status
+
* Follow up on past action items
 +
** ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
 +
** ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
 +
** Release Naming - Results of the TC poll - Next action
 +
 
 +
* New initiatives and/or report on previous initiatives
 +
** Help gmann on the community goals following our new goal process.
 +
*** It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
 +
** 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?
 +
** mnaser: sync up with swift team on python3 migration
 +
* addendums
 +
** define goal select process schedule
 +
*** 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
 +
** overall review for TC summit and PTG plans
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
  
* tbd
+
evrardjp - Travelling
  
 +
cloudnull - Holiday
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 13:41, 10 October 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: 10 October 2019
  • Chair: asettle
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
    • ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
    • Release Naming - Results of the TC poll - Next action
  • New initiatives and/or report on previous initiatives
    • Help gmann on the community goals following our new goal process.
      • It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
    • 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?
    • mnaser: sync up with swift team on python3 migration
  • addendums
    • define goal select process schedule
      • 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
    • overall review for TC summit and PTG plans

Apologies for Absence

evrardjp - Travelling

cloudnull - Holiday

Past meetings logs

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