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 2014|
|Russell Bryant (russellb)||October 2014|
|Thierry Carrez (ttx)||April 2014|
|Robert Collins (lifeless)||April 2014|
|Sean Dague (sdague)||October 2014|
|Anne Gentle (annegentle)||October 2014|
|John Griffith (jgriffith)||April 2014|
|Doug Hellmann (dhellmann)||October 2014|
|Vish Ishaya (vishy)||April 2014|
|Mark McClain (markmcclain)||April 2014|
|Mark McLoughlin (markmc)||October 2014|
|Michael Still (mikal)||April 2014|
|Monty Taylor (mordred)||October 2014|
The openstack-tc mailing-list is used for communication within the Technical Committee. Posting is moderated for non-members.
Next meeting: Tuesday Feb 4, 20:00 UTC
- Joshua McKenty and Rob Hirschfeld to raise some projects vs programs concerns identified through the Foundation Board's DefCore sub-committee
- Minor governance changes
- Open discussion
These items have been proposed, but have not been discussed on openstack-dev for the time mandated by our bylaws yet:
- Assert control over website and memberdata systems  -- pending ML thread
- Incubation request: Barbican -- pending ML thread
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 email@example.com, then a pointer to that thread should be posted to firstname.lastname@example.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.
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