Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 6: Line 6:
=== Next Meeting ===
=== Next Meeting ===
* January 26th, 20:00 UTC (to be confirmed)
* January 26th, 20:00 UTC (if quorum is reached)
* Chair: Flavio Percoco (flaper87)
* Chair: Flavio Percoco (flaper87)
Line 17: Line 17:
* Adding SaltStack to OpenStack [https://review.openstack.org/269556]
* Adding SaltStack to OpenStack [https://review.openstack.org/269556]
* improve licensing docs [https://review.openstack.org/269823]
* improve licensing docs [https://review.openstack.org/269823]
* More tbd
* Comms WG update
* Open discussion
* Open discussion
Line 29: Line 29:
==== Apologies for Absence ====
==== Apologies for Absence ====
* tbd
* ttx, sdague, jaypipes

Revision as of 10:47, 22 January 2016

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

  • January 26th, 20:00 UTC (if quorum is reached)
  • Chair: Flavio Percoco (flaper87)


  • remove expired extra ATCs [1]
  • Applying for a EC2API replacement project. [2]
  • add new Repo(shovel) to the Governance Repository [3]
  • Adding SaltStack to OpenStack [4]
  • improve licensing docs [5]
  • Comms WG update
  • 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:

  • Remove containers from Nova's mission [6] (needs an update)

Apologies for Absence

  • ttx, sdague, jaypipes

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