Jump to: navigation, search


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

Next Meeting

  • May 31st, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


  • Add resolution explaining which tests we think defcore should use [1]
  • Add resolution asking defcore committee to avoid using proxy APIs in tests [2]
  • Add Juju Charms for OpenStack [3]
  • Add golang as an approved language [4] - coming up to a decision
  • Open discussion


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:

  • Add project Vitrage to OpenStack big-tent [5] (backlog)
  • Add project Watcher to OpenStack big-tent [6] (backlog)
  • Trim tc-approved-release tag to just base IaaS projects [7] (pending update)
  • Adds a docs:devdocs tag to indicate if project publishes devdocs [8] (pending update)
  • Call out GPL style licenses in testing/validation. [9] (pending an update)
  • type:packaging and type:deployment tags (pending iterations on the reviews)
    • Introduce type:deployment tag [10]
    • Introduce a type:packaging tag [11]
    • Modify asserts for upgrades to include deployment [12]
    • Add type:deployment to release:cycle_with_miestones [13]
  • Tidy of item 5 of the vulnerability:managed tag [14] (pending post-summit refresh)

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