Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

m (Next Meeting)
Line 18: Line 18:
 
** Move from program-based structure to project-based (including new projects requirements) [https://review.openstack.org/145740]
 
** Move from program-based structure to project-based (including new projects requirements) [https://review.openstack.org/145740]
 
* Adding python clients to global requirements [http://lists.openstack.org/pipermail/openstack-dev/2015-January/054275.html]
 
* Adding python clients to global requirements [http://lists.openstack.org/pipermail/openstack-dev/2015-January/054275.html]
 +
* How to drive more resources to critical oslo libs (vishy)
 
* Other governance changes
 
* Other governance changes
 
* Open discussion
 
* Open discussion
Line 25: Line 26:
 
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:
 
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:
  
* tbd
+
* Review openstack-specs approval rules
  
  
Line 31: Line 32:
  
 
* tbd
 
* tbd
 +
  
 
=== Presenting a motion before the TC ===
 
=== Presenting a motion before the TC ===

Revision as of 10:29, 14 January 2015


The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack governance website at http://governance.openstack.org . It meets weekly in an open meeting in the #openstack-meeting IRC channel on Freenode.


Next Meeting

  • January 20th, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


Agenda

  • Next Defcore steps (assuming bylaws amendments pass)
  • Project structure reform
    • Template for tags definition [1]
    • Definition of the initial 'integrated-release' tag [2] [3]
    • Move from program-based structure to project-based (including new projects requirements) [4]
  • Adding python clients to global requirements [5]
  • How to drive more resources to critical oslo libs (vishy)
  • Other governance changes
  • 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, or are just delayed while we process the earlier requests backlog:

  • Review openstack-specs approval rules


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