Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 6: Line 6:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* March 24th, 20:00 UTC
+
* March 31st, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
* Chair: Thierry Carrez (ttx)
  
Line 12: Line 12:
 
==== Agenda ====
 
==== Agenda ====
  
* openstack-specs final rubberstamping
 
** Add library stable release procedures/policy [https://review.openstack.org/#/c/155072/] ?
 
* Magnum - OpenStack Containers Service [https://review.openstack.org/161080]
 
 
* Add a tag for affiliation diversity [https://review.openstack.org/163851]
 
* Add a tag for affiliation diversity [https://review.openstack.org/163851]
* Add proposal to rename core teams as maintainer teams [https://review.openstack.org/163660]
+
* Add the Congress project [https://review.openstack.org/165204]
* Adding the Murano Application Catalog to OpenStack [https://review.openstack.org/#/c/162745/]
+
* tbd
 
* Housekeeping
 
* Housekeeping
** Adds puppet-bandersnatch to Infrastructure [https://review.openstack.org/163734]
+
** Adds the openstack/os-cloud-management to TripleO... [https://review.openstack.org/166723]
** Add oslo.cache to reference/projects.yaml [https://review.openstack.org/164342]
+
** Add os-testr repo to QA [https://review.openstack.org/167244]
** Add coreos-image-builder to Ironic [https://review.openstack.org/164370]
+
** Add ansible-puppet repo to infra [https://review.openstack.org/166820]
** Add puppet-puppet project [https://review.openstack.org/165438]
+
** Add ansible-build-image to infra [https://review.openstack.org/166821]
 +
** tbd
 
* Open discussion
 
* Open discussion
  
Line 29: Line 27:
 
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:
  
* Add the Congress project [https://review.openstack.org/165204]
 
 
* [WIP] Add Group Based Policy Project [https://review.openstack.org/161902]
 
* [WIP] Add Group Based Policy Project [https://review.openstack.org/161902]
 
* WIP: Add reference to running an election to new projects requirements [https://review.openstack.org/162789]
 
* WIP: Add reference to running an election to new projects requirements [https://review.openstack.org/162789]

Revision as of 09:29, 25 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 31st, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


Agenda

  • Add a tag for affiliation diversity [1]
  • Add the Congress project [2]
  • tbd
  • Housekeeping
    • Adds the openstack/os-cloud-management to TripleO... [3]
    • Add os-testr repo to QA [4]
    • Add ansible-puppet repo to infra [5]
    • Add ansible-build-image to infra [6]
    • 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:

  • [WIP] Add Group Based Policy Project [7]
  • WIP: Add reference to running an election to new projects requirements [8]
  • WIP - add some tags describing roles [9]


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