Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m (Agenda)
(Next Meeting)
 
(340 intermediate revisions by 22 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]].'''
 +
 
 +
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.
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* February 2nd, 20:00 UTC
+
* Date: 16 January 2020
* Chair: Thierry Carrez (ttx)
+
* Chair: evrardjp
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 +
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Follow up on past action items
 +
** ricolin: (in March 2020): Report on whether guidelines worked.
 +
** ttx: Report on large scale sig -- how does this fly and how are the action items.
 +
** mnaser: report on infra liaison and static hosting
 +
** ttx: report about the vision reflection update, that should be started in January
 +
** jungleboyj: report on the blog post for the analysis of the survey
 +
** ttx (report in Feb 2020): Report on tc/uc merge
 +
** mnaser: report on stable branch policy work.
  
* rescheduling bug-smash event - [http://lists.openstack.org/pipermail/openstack-dev/2016-January/085196.html] - dhellmann
+
* New initiatives and/or report on previous initiatives
* Open discussion
+
** gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
 +
*** anyone to help gmann?
 +
** ...
  
==== 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:
 
 
* Remove containers from Nova's mission [https://review.openstack.org/256440] (needs an update)
 
  
 +
* addendums
  
 
==== 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:37, 5 December 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: 16 January 2020
  • Chair: evrardjp
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: (in March 2020): Report on whether guidelines worked.
    • ttx: Report on large scale sig -- how does this fly and how are the action items.
    • mnaser: report on infra liaison and static hosting
    • ttx: report about the vision reflection update, that should be started in January
    • jungleboyj: report on the blog post for the analysis of the survey
    • ttx (report in Feb 2020): Report on tc/uc merge
    • mnaser: report on stable branch policy work.
  • New initiatives and/or report on previous initiatives
    • gmann report on the community goals for U and V, py2 drop, and goal select process schedule.
      • anyone to help gmann?
    • ...


  • addendums

Apologies for Absence

Past meetings logs

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