Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
Line 6: Line 6:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* February 17th, 20:00 UTC ('''might be skipped''')
+
* February 24th, 20:00 UTC
* Chair: Sean Dague (sdague)
+
* Chair: Thierry Carrez (ttx)
  
  
Line 17: Line 17:
 
* Projects using private communication channels [http://lists.openstack.org/pipermail/openstack-dev/2015-February/056551.html]
 
* Projects using private communication channels [http://lists.openstack.org/pipermail/openstack-dev/2015-February/056551.html]
 
* Other governance changes
 
* Other governance changes
** Add Cinder's os-brick library to cinder [https://review.openstack.org/153673]
+
** tbd
** Adding Piet Kruithof as Horizon ATC [https://review.openstack.org/154271]
 
 
* Open discussion
 
* Open discussion
  

Revision as of 09:53, 18 February 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

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


Agenda

  • Final rubberstamp on CLI Sorting Argument Guidelines [1]
  • M+ Release naming process [2]
  • openstack-specs approval rules
  • Projects using private communication channels [3]
  • 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, or are just delayed while we process the earlier requests backlog:

  • tbd


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