Difference between revisions of "Meetings/TechnicalCommittee"
(→Meeting) |
|||
Line 61: | Line 61: | ||
==== Agenda ==== | ==== Agenda ==== | ||
− | * Integrated projects and new requirements: Gap analysis for | + | * Integrated projects and new requirements: Gap analysis for Keystone |
* Minor governance changes | * Minor governance changes | ||
** tbd | ** tbd | ||
Line 69: | Line 69: | ||
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: | 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: | ||
− | * Integrated projects and new requirements: Review Neutron plan to cover gap [https://etherpad.openstack.org/p/neutron-nova-parity] (waiting for plan to be signed off by neutron-core, | + | * Integrated projects and new requirements: Gap analysis for Ceilometer (Apr 8) |
+ | * Integrated projects and new requirements: Gap analysis for Trove (Apr 8) | ||
+ | * Integrated projects and new requirements: Gap analysis for Glance (?) | ||
+ | * Integrated projects and new requirements: Review Neutron plan to cover gap [https://etherpad.openstack.org/p/neutron-nova-parity] (waiting for plan to be signed off by neutron-core, April 15?) | ||
+ | * Integrated projects and new requirements: Gap analysis for Swift | ||
+ | * Integrated projects and new requirements: Gap analysis for Horizon | ||
+ | * Integrated projects and new requirements: Gap analysis for Heat | ||
==== Apologies for Absence ==== | ==== Apologies for Absence ==== |
Revision as of 10:56, 27 March 2014
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.
The Technical Committee is formally defined in the OpenStack Foundation bylaws (in particular article 4.1(b), article 4.13 and Appendix 4) and further refined in the Technical Committee charter.
Members
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 |
Mailing-list
The openstack-tc mailing-list is used for communication within the Technical Committee. Posting is moderated for non-members.
Meeting
Next meeting: Tuesday April 1st, 20:00 UTC
Agenda
- Integrated projects and new requirements: Gap analysis for Keystone
- Minor governance changes
- tbd
- 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 bylaws yet, or are blocked for some other reason:
- Integrated projects and new requirements: Gap analysis for Ceilometer (Apr 8)
- Integrated projects and new requirements: Gap analysis for Trove (Apr 8)
- Integrated projects and new requirements: Gap analysis for Glance (?)
- Integrated projects and new requirements: Review Neutron plan to cover gap [1] (waiting for plan to be signed off by neutron-core, April 15?)
- Integrated projects and new requirements: Gap analysis for Swift
- Integrated projects and new requirements: Gap analysis for Horizon
- Integrated projects and new requirements: Gap analysis for Heat
Apologies for Absence
- tbd
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 openstack-dev@lists.openstack.org, then 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.
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