Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting: Prepared next meeting.)
 
(135 intermediate revisions by 15 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.
  
* May 2nd, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
  
 +
=== Next Meeting ===
  
==== Agenda ====
+
* Date: 5 March 2020
 +
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
* Elect chair [https://review.openstack.org/458774] (add your candidacy here)
+
==== Agenda Suggestions ====
* More tbd
 
* Open discussion
 
  
 +
* Follow up on past action items
  
==== Backlog ====
+
* Ensuring ttx did report on the ML for the large scale sig
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:
+
* Report on tc/uc merge (ttx)
 
+
* Ensuring the analysis of the survey was updated (jungleboyj)
* Describe what upstream support means [https://review.openstack.org/440601] (might be unnecessary if we decide to contract for technical reasons)
+
* Report on telemetry after Rico's convo with the PTL (ricolin)
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (work in progress)
+
* report on stable branch policy work: mnaser to push an update to distill what happened on the ML in terms of stable branch policy (mnaser)
* deprecate postgresql in OpenStack [https://review.openstack.org/427880] (needs clarity about whether we would drop it even if we received support, forum discussion)
+
* report on the community goals for U and V, py2 drop (gmann)
* assert:supports-api-compatibility tag [https://review.openstack.org/418010] (pending API change guidelines update [https://review.openstack.org/421846])
+
* report on release naming (mugsie)
* Draft technical committee vision for public feedback [https://review.openstack.org/453262] (waiting for feedback)
+
* report on the ideas repo on the ML when ready (evrardjp)
* Fix comment about design summits [https://review.openstack.org/454070] (waiting for new revision)
+
* volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
 +
* Report on the OSF board initiatives (evrardjp)
 +
* Dropping side projects: using golden signals (ttx). ttx will list signals, and later projects matching those.
  
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
* tbd
 
 
 
=== 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 15:15, 6 February 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: 5 March 2020
  • Chair: evrardjp
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
  • Ensuring ttx did report on the ML for the large scale sig
  • Report on tc/uc merge (ttx)
  • Ensuring the analysis of the survey was updated (jungleboyj)
  • Report on telemetry after Rico's convo with the PTL (ricolin)
  • report on stable branch policy work: mnaser to push an update to distill what happened on the ML in terms of stable branch policy (mnaser)
  • report on the community goals for U and V, py2 drop (gmann)
  • report on release naming (mugsie)
  • report on the ideas repo on the ML when ready (evrardjp)
  • volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
  • Report on the OSF board initiatives (evrardjp)
  • Dropping side projects: using golden signals (ttx). ttx will list signals, and later projects matching those.


Apologies for Absence

Past meetings logs

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