The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters.
|Name||Election||End of term|
|Russell Bryant (russellb)||Nova PTL||Fall 2013|
|Thierry Carrez (ttx)||Chair, Directly-elected||Spring 2014|
|Julien Danjou (jd__)||Ceilometer PTL||Fall 2013|
|John Dickinson (notmyname)||Swift PTL||Fall 2013|
|Anne Gentle (annegentle)||Directly-elected||Fall 2013|
|John Griffith (jgriffith)||Cinder PTL||Fall 2013|
|Steven Hardy (shardy)||Heat PTL||Fall 2013|
|Gabriel Hurley (gabrielhurley)||Horizon PTL||Fall 2013|
|Vish Ishaya (vishy)||Directly-elected||Spring 2014|
|Dolph Mathews (dolphm)||Keystone PTL||Fall 2013|
|Mark McClain (markmcclain)||Quantum PTL||Fall 2013|
|Mark McLoughlin (markmc)||Oslo PTL||Fall 2013|
|Mikal Still (mikal)||Directly-elected||Fall 2013|
|Monty Taylor (mordred)||Directly-elected||Fall 2013|
|Mark Washenberger (markwash)||Glance PTL||Fall 2013|
The openstack-tc mailing-list is used for communication within the Technical Committee. Posting is moderated for non-members.
Next meeting: July 16, 2013
- New program application: TripleO
- Scope, mission statement, how "essential" the effort is to OpenStack
- Team/effort/community maturity
- Open discussion:
- Preliminary discussion on devstack application as a program 
- Should vulnerability management, release management and/or stable branch management also be program(s) ?
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 firstname.lastname@example.org and CC-ed to email@example.com. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc