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

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


  • Adding MagnetoDB to OpenStack [1]
  • Adding the Puppet modules to OpenStack [2]
  • Let projects add repos without prior-approval [3]
  • Projects list housekeeping
    • Add glean to infra [4]
    • Rename keystoneclient-federation to saml2 [5]
    • Add django-openstack-auth-kerberos project [6]
    • Changes Rally to Benchmark service to better match other names [7]
  • Governance repo housekeeping
    • Update sphinx docs to support team based tags [8]
    • Remove unused code from teams.py [9]
    • Update formatting of teams page [10]
    • Update diversity.py to use projects.yaml [11]
    • Add tool/framework to automatically validate the tag applications. [12]
    • Add check for 'release:has-stable-branches' [13]
  • Open discussion
    • Cross-project track at the Design Summit [14]


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 bylaws yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:

  • Add 'regulatory' to congress service name [15] (pending progress on approval)
  • Adding the Chef cookbooks to OpenStack [16] (planned Apr 27)
  • Updated based on PTL elections [17] (needs election officials +1)
  • WIP - Add Group Based Policy Project [18] (marked WIP)
  • WIP: Add reference to running an election to new projects requirements [19] (marked WIP)
  • WIP - add some tags describing roles [20] (marked WIP)

Apologies for Absence

  • tbd

Presenting a motion before the TC

Motions need to be presented at least 4 business days before the next meeting scheduled time. They should be posted to openstack-dev@lists.openstack.org, then 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.

Note that before being voted on, motions must now be presented as a governance change.

Past meetings logs

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