Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
Line 19: Line 19:
 
* Add release:managed to libraries [https://review.openstack.org/191893] and previously-incubated projects [https://review.openstack.org/192193]
 
* Add release:managed to libraries [https://review.openstack.org/191893] and previously-incubated projects [https://review.openstack.org/192193]
 
* CLA / DCO workplan on Board Agenda [http://lists.openstack.org/pipermail/foundation-board/2015-June/000074.html]
 
* CLA / DCO workplan on Board Agenda [http://lists.openstack.org/pipermail/foundation-board/2015-June/000074.html]
 +
* Be specific about geography in release names [https://review.openstack.org/191974]
 
* Workgroup reports
 
* Workgroup reports
 
* Open discussion
 
* Open discussion
 +
  
 
==== Backlog ====
 
==== Backlog ====
Line 26: Line 28:
  
 
* RPM distribution packaging of OpenStack [https://review.openstack.org/191587]
 
* RPM distribution packaging of OpenStack [https://review.openstack.org/191587]
* Be specific about geography in release names [https://review.openstack.org/191974]
 
 
* Move stackforge to openstack [https://review.openstack.org/192016]
 
* Move stackforge to openstack [https://review.openstack.org/192016]
 +
* Be less proscriptive about new team size/maturity [https://review.openstack.org/193550]
 
* Adding distribution packaging to OpenStack [https://review.openstack.org/185187] (pending narrowing of scope)
 
* Adding distribution packaging to OpenStack [https://review.openstack.org/185187] (pending narrowing of scope)
 
* Ironic is considering changing their release cycle [https://review.openstack.org/185203] (pending spec at https://review.openstack.org/#/c/185171/)
 
* Ironic is considering changing their release cycle [https://review.openstack.org/185203] (pending spec at https://review.openstack.org/#/c/185171/)

Revision as of 08:27, 22 June 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

  • June 23rd, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


Agenda

  • Add compute starter kit tag (final approval) [1]
  • Ansible playbooks and roles to deploy OpenStack [2]
  • Add Cue Message Broker Service to Openstack: [3]
  • Add Solum to OpenStack Projects List [4]
  • Add type:library and type:service tags [5] [6]
  • Add release:managed to libraries [7] and previously-incubated projects [8]
  • CLA / DCO workplan on Board Agenda [9]
  • Be specific about geography in release names [10]
  • Workgroup reports
  • 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 charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:

  • RPM distribution packaging of OpenStack [11]
  • Move stackforge to openstack [12]
  • Be less proscriptive about new team size/maturity [13]
  • Adding distribution packaging to OpenStack [14] (pending narrowing of scope)
  • Ironic is considering changing their release cycle [15] (pending spec at https://review.openstack.org/#/c/185171/)
  • WIP - Add Group Based Policy Project [16] (marked WIP)
  • WIP - add some tags describing roles [17] (marked WIP)


Apologies for Absence

  • tbd


Proposing discussion topics, motions or other governance changes before the TC

Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the governance repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with 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.

Before being finally voted on, motions will have to be presented as a governance change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.

Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.


Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc