Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 6: Line 6:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* March 3rd, 20:00 UTC
+
* March 10th, 20:00 UTC (to be confirmed)
* Chair: Thierry Carrez (ttx)
+
* Chair: Jim Blair (jeblair)
  
  
 
==== Agenda ====
 
==== Agenda ====
  
* openstack-specs final rubberstamping
+
* Add IRC channel policies [https://review.openstack.org/159930]
** Add TRACE definition to log guidelines [https://review.openstack.org/#/c/145245]
+
* Magnum - OpenStack Containers Service [https://review.openstack.org/161080]
 
* Definition of the release:* tags [https://review.openstack.org/157322]
 
* Definition of the release:* tags [https://review.openstack.org/157322]
 
* Other governance changes
 
* Other governance changes
** Add ironic-lib to Ironic program [https://review.openstack.org/157757]
+
** Add the new developer-reference repo to the TC list [https://review.openstack.org/161009]
** Add dib-utils as part of TripleO [https://review.openstack.org/158365]
+
** Remove py26 from PTI [https://review.openstack.org/159936]
** Add mission statement for project 'Heat' [https://review.openstack.org/154049]
+
** Remove reference to Jenkins in PTI [https://review.openstack.org/159935]
** Adding Piet Kruithof as Horizon ATC [https://review.openstack.org/154271]
 
 
* Housekeeping
 
* Housekeeping
** Build list of teams from YAML file [https://review.openstack.org/125788]
+
** Add .pyc files to gitignore [https://review.openstack.org/161023]
 
** Update the Infrastructure project homepage URL [https://review.openstack.org/158371]
 
** Update the Infrastructure project homepage URL [https://review.openstack.org/158371]
** Improve the doc build process (openstack-specs) [https://review.openstack.org/#/c/156715/]
 
 
* Open discussion
 
* Open discussion
** Ops Summit in PHL next week
 
  
  
Line 32: Line 29:
  
 
* Final rubberstamping of "Cross-Project spec to eliminate SQL Schema Downgrades" [https://review.openstack.org/#/c/152337/] -- wait until after Ops summit
 
* Final rubberstamping of "Cross-Project spec to eliminate SQL Schema Downgrades" [https://review.openstack.org/#/c/152337/] -- wait until after Ops summit
* Add IRC channel policies [https://review.openstack.org/159930] (proposed too late for this weeks meeting)
 
* Remove reference to Jenkins in PTI [https://review.openstack.org/159935] (proposed too late for this weeks meeting)
 
* Remove py26 from PTI [https://review.openstack.org/159936] (proposed too late for this weeks meeting)
 
  
  

Revision as of 09:36, 4 March 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

  • March 10th, 20:00 UTC (to be confirmed)
  • Chair: Jim Blair (jeblair)


Agenda

  • Add IRC channel policies [1]
  • Magnum - OpenStack Containers Service [2]
  • Definition of the release:* tags [3]
  • Other governance changes
    • Add the new developer-reference repo to the TC list [4]
    • Remove py26 from PTI [5]
    • Remove reference to Jenkins in PTI [6]
  • Housekeeping
    • Add .pyc files to gitignore [7]
    • Update the Infrastructure project homepage URL [8]
  • 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:

  • Final rubberstamping of "Cross-Project spec to eliminate SQL Schema Downgrades" [9] -- wait until after Ops summit


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