Jump to: navigation, search


< Meetings
Revision as of 14:14, 31 March 2015 by Annegentle (talk | contribs) (Next Meeting)

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

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


  • Final rubberstamp on "Add library stable release procedures/policy" [1]
  • Add the Congress project [2]
  • Apply release:* tags to current projects [3]
    • Should we tag git repositories or "deliverables" (collections of OpenStack software code repositories released together) ?
  • Projects list housekeeping
    • Adds the openstack/os-cloud-management to TripleO... [4]
    • Add os-testr repo to QA [5]
    • Add ansible-puppet repo to infra [6]
    • Add ansible-build-image to infra [7]
    • Add bashate to the QA program [8]
    • Add puppet-diskimage-builder to Infra [9]
    • Move os-client-config to openstack namepsace [10]
  • Open discussion
    • Neutron renaming "core reviewers" to "maintainers" [11]
    • WIP: Add Group Based Policy Project [12]
    • WIP: add some tags describing roles [13]


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:

  • Defcore process [14] discussion -- scheduled for Apr 7 meeting
  • WIP: Add reference to running an election to new projects requirements [15]
  • WIP: Need guidance for docs.openstack.org publishing and brand guidelines, especially for newest projects [16]

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