Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Meeting)
(Meeting)
Line 57: Line 57:
 
=== Meeting ===
 
=== Meeting ===
  
Next meeting: Tuesday July 15th, 20:00 UTC
+
Next meeting: Tuesday July 29th, 20:00 UTC
  
 
==== Agenda ====
 
==== Agenda ====
  
* Core Capabilities TC scoring [https://review.openstack.org/100722]
+
* Check progress on gap coverage plans (post-j2 edition)
* Integrated projects and new requirements: Gap analysis for Heat [https://etherpad.openstack.org/p/heat-gap-analysis]
+
* Blessing Heat gap coverage plan
* Election behavior guidelines redux
+
* Block Storage abstractions in Cinder [http://lists.openstack.org/pipermail/openstack-tc/2014-July/000736.html] (to be confirmed)
** 2014-07-11 Election Activities [https://review.openstack.org/106557]
+
* Other governance changes
** A resolution on standards of behavior during elections [https://review.openstack.org/100445]
+
** tbd
** Adds a resolution addressing expected election behaviour [https://review.openstack.org/98675]
 
* Pending governance changes
 
** Adding Horizon mission statement [https://review.openstack.org/102050]
 
** Add translation support requirement [https://review.openstack.org/97872]
 
 
* Open discussion
 
* Open discussion
 +
  
 
==== Backlog ====
 
==== 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:
 
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:
  
* Block Storage abstractions in Cinder [http://lists.openstack.org/pipermail/openstack-tc/2014-July/000736.html]
+
* Integrated projects and new requirements: Gap analysis for Swift [https://etherpad.openstack.org/p/swift_gap_analysis] (planned August 5)
* Integrated projects and new requirements: Gap analysis for Swift, July 22 or August 5 [https://etherpad.openstack.org/p/swift_gap_analysis]
 
  
  

Revision as of 08:00, 16 July 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 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

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 July 29th, 20:00 UTC

Agenda

  • Check progress on gap coverage plans (post-j2 edition)
  • Blessing Heat gap coverage plan
  • Block Storage abstractions in Cinder [1] (to be confirmed)
  • Other 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 Swift [2] (planned August 5)


At every milestone we should review progress on the incubation/integration gap coverage plans:

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