Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Apologies for Absence)
(Next Meeting)
 
(172 intermediate revisions by 21 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.
  
* March 21st, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
  
 +
=== Next Meeting ===
  
==== Agenda ====
+
* Date: August 6th, 2020
 +
* Chair: Mohammed Naser
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
  
* Add naming poll info for R release [https://review.openstack.org/445733]
+
==== Agenda Suggestions ====
* Add Golang CTI [https://review.openstack.org/410355]
 
* Add a "docs:install-guide-verified" tag [https://review.openstack.org/445536]
 
* Add tag assert:never-breaks-compat [https://review.openstack.org/446561]
 
* Open discussion
 
** FYI on Unified Limits in Keystone Spec [https://review.openstack.org/#/c/440815/] and ML [http://lists.openstack.org/pipermail/openstack-dev/2017-March/114230.html] (sdague) - want to ensure TC folks are aware of this and weigh in where appropriate
 
** Moving Split out tempest plugins [https://review.openstack.org/369749] to Queens potential goals
 
** Vision exercise feedback
 
** Forum topics
 
 
 
==== 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:
 
 
 
* Move shade into its own top-level team [https://review.openstack.org/446426] (planned for March 28)
 
* Driver teams [https://review.openstack.org/403829] [https://review.openstack.org/403836] and networking-cisco's standing request [https://review.openstack.org/363709] (deferred until Doug and Mike are both around)
 
* Describe what upstream support means [https://review.openstack.org/440601] (might be unnecessary if we decide to contract for technical reasons)
 
* deprecate postgresql in OpenStack [https://review.openstack.org/427880] (needs clarity about whether we would drop it even if we received support)
 
* assert:supports-api-compatibility tag [https://review.openstack.org/418010] (pending API change guidelines update [https://review.openstack.org/421846])
 
  
 +
* Follow up on past action items
 +
* OpenStack User-facing APIs and CLIs (belmoreira)
 +
* W cycle goal selection start
 +
* Completion of retirement cleanup (gmann)
 +
** https://etherpad.opendev.org/p/tc-retirement-cleanup
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* dhellmann - 21 March and 28 March, PTO
 
* mtreinish (on a plane again)
 
 
=== 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 16:53, 4 August 2020


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: August 6th, 2020
  • Chair: Mohammed Naser
  • Agenda to be published on the OpenStack-discuss mailing list before the meeting

Agenda Suggestions

Apologies for Absence

Past meetings logs

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