Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 09:54, 29 August 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

• August 30th, 20:00 UTC
• Chair: Thierry Carrez (ttx)

Agenda

• Extra ATCs
  • Adds winstackers extra ATCs list [1]
  • Add Bryan Sullivan as extra-ATC for Congress [2]
• Update Glance mission statement [3]
• Add the newly-created Requirements team to projects.yaml [4]
• New Storlets project team [5]
• Goals
  • expand goal template with info about current state [6]
  • propose approval policy for goal responses [7]
  • Revises technical debt wording and fix typos in goals document [8]
  • add ocata goal "support python 3.5" [9]
• Open discussion

Backlog

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:

• Mention where the metric rules are defined/used [10] (deferred to next meeting)
• Write down OpenStack principles [11] (deferred to next meeting)
• Equal Integration Chances for all Projects [12] (round 2) (WIP)
• Add project Tricircle to OpenStack big-tent [13] (deferred, mordred to drive)
• Add Cross Project Liason imformation to projects.yaml [14] (WIP)

Apologies for Absence

• thingee August 30 & September 6 (Burning man)

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