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 2014|
|Thierry Carrez (ttx)||April 2015|
|Sean Dague (sdague)||October 2014|
|Anne Gentle (annegentle)||October 2014|
|Doug Hellmann (dhellmann)||October 2014|
|Vish Ishaya (vishy)||April 2015|
|Mark McClain (markmcclain)||April 2015|
|Mark McLoughlin (markmc)||October 2014|
|Jay Pipes (jaypipes)||April 2015|
|Michael Still (mikal)||April 2015|
|Monty Taylor (mordred)||October 2014|
|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: Tuesday September 30th, 20:00 UTC
- Recommendation to Adopt DCO as CLA 
- Add a docs environment to the testing interface 
- Remove support for specific public cloud implementations from our code 
- Other governance changes
- Open discussion
- Layer #1 and the big tent
- Shelved discussions while we figure it out:
- Deeper dive into Swift "differences"
- Kilo plan for Zaqar
- Need for TC meetings during TC election season (next two weeks) ?
- Gap coverage plans final status
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:
At every milestone we should review progress on the incubation/integration gap coverage plans:
- Neutron gap coverage plan
- Trove gap coverage plan
- Ceilometer gap coverage plan
- Horizon gap coverage plan
- Glance gap coverage plan
- Heat gap coverage plan
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