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||End of term|
|James E. Blair (jeblair)||April 2015|
|Russell Bryant (russellb)||October 2015|
|Thierry Carrez (ttx)||April 2015|
|Sean Dague (sdague)||October 2015|
|Anne Gentle (annegentle)||October 2015|
|John Griffith (jgriffith)||October 2015|
|Doug Hellmann (dhellmann)||October 2015|
|Vish Ishaya (vishy)||April 2015|
|Mark McClain (markmcclain)||April 2015|
|Jay Pipes (jaypipes)||April 2015|
|Michael Still (mikal)||April 2015|
|Monty Taylor (mordred)||October 2015|
|Devananda van der Veen (devananda)||April 2015|
The openstack-tc mailing-list is used for communication within the Technical Committee. Posting is moderated for non-members.
Next meeting: December 9, 20:00 UTC
- Project structure reform spec 
- Housekeeping changes
- 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 bylaws yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:
- A TC mentor for each incubated project ? (pending future of incubation)
Apologies for Absence
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, then a pointer to that thread should be posted to email@example.com 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