Difference between revisions of "Meetings/TechnicalCommittee"

Revision as of 13:27, 16 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 16th, 20:00 UTC
• Chair: Thierry Carrez (ttx)

Agenda

• Appoint Dean Troyer as replacement for Morgan [1]
• Community-wide goals [2] [3] [4] (final approval)
• Storlets [5] (initial discussion)
• 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:

• Update Glance mission statement [6] (WIP)
• Equal Integration Chances for all Projects [7] (round 2) (WIP)
• Split out the requirements repo into its own team [8] (WIP)
• Clarify what an active (core) reviewer is [9] (WIP)
• Add project Tricircle to OpenStack big-tent [10] (deferred, mordred to drive)
• Add Cross Project Liason imformation to projects.yaml [11] (WIP)

Apologies for Absence

• flaper87 August 16
• dims August 16
• thingee August 16, 23, 30 (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