Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
(Meeting)
Line 57: Line 57:
 
=== Meeting ===
 
=== Meeting ===
  
Next meeting: Tuesday June 24th, 20:00 UTC
+
Next meeting: Tuesday July 1st, 20:00 UTC
  
 
==== Agenda ====
 
==== Agenda ====
  
* Glance gap coverage plan [https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Glance_Gap_Coverage]
+
Single-topic meeting about Defcore:
* Other governance changes in review
+
* Tension around asking the representation of contributors to designate parts of OpenStack that just may be replaced by proprietary alternatives
** Modify Images mission to fit Artifact Repository [https://review.openstack.org/98002]
+
* Tension around not calling part of what the OpenStack community produces "OpenStack"
** Add translation support requirement [https://review.openstack.org/97872]
+
* Requested input: Designated sections
* Defcore
+
* Requested input: "TC direction" scoring on core capabilities
** Resolution requesting designated sections from projects [https://review.openstack.org/100675]
+
* Scoring process for future iterations of Defcore
** Propose scores for DefCore capabilities [https://review.openstack.org/100721] [https://review.openstack.org/100722]
 
* Election behavior guidelines
 
** Adds a resolution addressing expected election behaviour [https://review.openstack.org/98675]
 
** A resolution on standards of behavior during elections [https://review.openstack.org/100445]
 
 
* 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:
  
* Scoring process for future iterations of Defcore
+
* Election behavior guidelines (will be back next week)
 
* Integrated projects and new requirements: Gap analysis for Swift
 
* Integrated projects and new requirements: Gap analysis for Swift
 
* Integrated projects and new requirements: Gap analysis for Heat
 
* Integrated projects and new requirements: Gap analysis for Heat
Line 86: Line 83:
 
* [[Governance/TechnicalCommittee/Ceilometer_Gap_Coverage|Ceilometer gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Ceilometer_Gap_Coverage|Ceilometer gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Horizon_Gap_Coverage|Horizon gap coverage plan]]
 
* [[Governance/TechnicalCommittee/Horizon_Gap_Coverage|Horizon gap coverage plan]]
 +
* [[Governance/TechnicalCommittee/Glance_Gap_Coverage|Glance gap coverage plan]]
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====

Revision as of 08:51, 25 June 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 1st, 20:00 UTC

Agenda

Single-topic meeting about Defcore:

  • Tension around asking the representation of contributors to designate parts of OpenStack that just may be replaced by proprietary alternatives
  • Tension around not calling part of what the OpenStack community produces "OpenStack"
  • Requested input: Designated sections
  • Requested input: "TC direction" scoring on core capabilities
  • Scoring process for future iterations of Defcore
  • 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:

  • Election behavior guidelines (will be back next week)
  • Integrated projects and new requirements: Gap analysis for Swift
  • Integrated projects and new requirements: Gap analysis for Heat


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