Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Apologies for Absence)
 
(174 intermediate revisions by 19 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
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/ . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.
+
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-discuss mailing-list. '''We track current initiatives on the [[Technical_Committee_Tracker]].'''
  
=== Next Meeting ===
+
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.
  
* January 17th, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
 
 
==== Agenda ====
 
 
* Refresh I18n ATC list [https://review.openstack.org/417569]
 
* Amend new-language reference document [https://review.openstack.org/418487]
 
* Pike goal: support python 3.5 [https://review.openstack.org/349069]
 
* Pike goal: split out tempest plugins [https://review.openstack.org/369749]
 
* Pike goal: deploy-api-in-wsgi [https://review.openstack.org/419706]
 
* Introduce assert:supports-api-compatibility [https://review.openstack.org/418010]
 
* Open discussion
 
** Date/location for Board+TC workshop on OpenStack Futures
 
** Base services
 
** Next steps for Golang
 
  
 +
=== Next Meeting ===
  
 +
* Date: 10 October 2019
 +
* Chair: asettle
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
==== Backlog ====
+
==== Agenda Suggestions ====
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:
 
  
* Disallow downtime of controlled resources during upgrades [https://review.openstack.org/404361] [https://review.openstack.org/410329] (Jan 24; needs more discussion on the review)
+
* Follow up on past action items
* Driver teams decision [https://review.openstack.org/403829] [https://review.openstack.org/403836] (Jan 24? Feb 7? paused for a couple of weeks to get discovery work started first)
+
** ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
* Add networking-cisco back into the Big Tent [https://review.openstack.org/363709] (deferred until we get to a decision on driver teams)
+
** ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
* Equal Integration Chances for all Projects [https://review.openstack.org/342366] (needs round 2)
+
** 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 ====
  
* mtreinish
+
evrardjp - Travelling
 
 
=== Proposing discussion topics, motions or other governance changes before the TC ===
 
 
 
Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
 
 
 
Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.
 
 
 
Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.
 
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 12:35, 28 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

Past meetings logs

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