Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Absence)
 
(553 intermediate revisions by 37 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
The [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]] is one of the [[Governance|governing bodies]] of the OpenStack project. You can find more information about it, such as the list of its [http://governance.openstack.org current members] or its [http://governance.openstack.org/reference/charter.html governance charter], on the OpenStack governance website at http://governance.openstack.org . 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 [http://eavesdrop.openstack.org/#Technical_Committee_Meeting each week] in  #openstack-tc
  
* January 3rd, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
 
 
==== Agenda ====
 
 
* Driver teams: establish new "driver team" concept [https://review.openstack.org/403829] or not [https://review.openstack.org/403836]
 
* Disallow downtime of controlled resources during upgrades [https://review.openstack.org/404361] [https://review.openstack.org/410329]
 
* Pike goals
 
** Add Pike goal split out tempest plugins [https://review.openstack.org/369749]
 
** add goal "support python 3.5" [https://review.openstack.org/349069]
 
* Open discussion
 
 
 
==== Backlog ====
 
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:
 
 
* Reference doc for new language additions [https://review.openstack.org/398875] (Jan 10 meeting)
 
* Add extra-atc nominations for Trove [https://review.openstack.org/414764] (Jan 10 meeting)
 
* Add networking-cisco back into the Big Tent [https://review.openstack.org/363709] (deferred until we get to a decision on driver teams)
 
* Visions for the TC and OpenStack [https://review.openstack.org/401225] [https://review.openstack.org/401226] (to be moved to SWG for building up an initial draft)
 
* Equal Integration Chances for all Projects [https://review.openstack.org/342366] (needs round 2)
 
 
 
==== Apologies for Absence ====
 
 
* flaper87 (Jan 3rd meeting)
 
  
 +
=== Next Meeting ===
  
=== Proposing discussion topics, motions or other governance changes before the TC ===
+
* Date:  2022 Aug 11
 +
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
 +
* Chair: Ghanshyam Mann
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
 +
* Location: IRC OFTC network in the #openstack-tc channel
  
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.
+
==== Agenda Suggestions ====
  
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.
+
* Roll call
 +
* Follow up on past action items
 +
* Gate health check
 +
** Bare 'recheck' state
 +
*** https://etherpad.opendev.org/p/recheck-weekly-summary
 +
* 2023.1 cycle PTG Planning
 +
** https://framadate.org/Migjz5j4SZgx8PTa
 +
* Open Reviews
 +
** https://review.opendev.org/q/projects:openstack/governance+is:open
  
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.
+
==== Absence ====
 +
<Please write your name if you are not able to attend the meeting>
  
 +
* arne_wiebalck (will miss 4 August and 11 August)
 +
* slaweq (will miss 11 August)
 +
* Jay Bryant (jungleboyj) -- Will miss 8/11 due to Out of Office
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 17:29, 8 August 2022


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 each week in #openstack-tc


Next Meeting

Agenda Suggestions

Absence

<Please write your name if you are not able to attend the meeting>

  • arne_wiebalck (will miss 4 August and 11 August)
  • slaweq (will miss 11 August)
  • Jay Bryant (jungleboyj) -- Will miss 8/11 due to Out of Office

Past meetings logs

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