Jump to: navigation, search


< Meetings
Revision as of 14:07, 20 March 2017 by Treinish (talk | contribs) (Apologies for Absence)

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/ . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode.

Next Meeting

  • March 21st, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


  • Add naming poll info for R release [1]
  • Add Golang CTI [2]
  • Add a "docs:install-guide-verified" tag [3]
  • Add tag assert:never-breaks-compat [4]
  • Open discussion
    • FYI on Unified Limits in Keystone Spec [5] and ML [6] (sdague) - want to ensure TC folks are aware of this and weigh in where appropriate
    • Moving Split out tempest plugins [7] to Queens potential goals
    • Vision exercise feedback
    • Forum topics


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 [8] (planned for March 28)
  • Driver teams [9] [10] and networking-cisco's standing request [11] (deferred until Doug and Mike are both around)
  • Describe what upstream support means [12] (might be unnecessary if we decide to contract for technical reasons)
  • deprecate postgresql in OpenStack [13] (needs clarity about whether we would drop it even if we received support)
  • assert:supports-api-compatibility tag [14] (pending API change guidelines update [15])

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 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 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

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