Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
Line 13: Line 13:
  
 
* Rearrange presentation of Principles [https://review.openstack.org/394786]
 
* Rearrange presentation of Principles [https://review.openstack.org/394786]
 +
* Prefer voluntary participation [https://review.openstack.org/398540]
 +
* We value clear, friendly and open communication [https://review.openstack.org/365590]
 
* Update Python CTI for 3.5 [https://review.openstack.org/397501]
 
* Update Python CTI for 3.5 [https://review.openstack.org/397501]
 
* Acknowledge nominal prerequisites for tests [https://review.openstack.org/397502]
 
* Acknowledge nominal prerequisites for tests [https://review.openstack.org/397502]
* We value clear, friendly and open communication [https://review.openstack.org/365590]
 
 
* Review of Ocata goal acknowledgements
 
* Review of Ocata goal acknowledgements
* More tbd
+
* Add project Octavia to OpenStack big-tent [https://review.openstack.org/313056] (initial discussion)
 
* Open discussion
 
* Open discussion
 +
  
 
==== Backlog ====
 
==== 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:
 
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:
  
 +
* Reference doc for new language additions [https://review.openstack.org/398875] (deferred to Nov 29)
 
* Add networking-cisco back into the Big Tent [https://review.openstack.org/363709] (deferred until dhellmann files proposal for driver-only teams)
 
* Add networking-cisco back into the Big Tent [https://review.openstack.org/363709] (deferred until dhellmann files proposal for driver-only teams)
 
* Storlets to become official - Proposed governance change [https://review.openstack.org/353693] (missing items tracking at [https://etherpad.openstack.org/p/storlets-big-tent])
 
* Storlets to become official - Proposed governance change [https://review.openstack.org/353693] (missing items tracking at [https://etherpad.openstack.org/p/storlets-big-tent])

Revision as of 09:50, 18 November 2016


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

  • November 22nd, 20:00 UTC
  • Chair: Doug Hellmann (dhellmann)


Agenda

  • Rearrange presentation of Principles [1]
  • Prefer voluntary participation [2]
  • We value clear, friendly and open communication [3]
  • Update Python CTI for 3.5 [4]
  • Acknowledge nominal prerequisites for tests [5]
  • Review of Ocata goal acknowledgements
  • Add project Octavia to OpenStack big-tent [6] (initial discussion)
  • 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:

  • Reference doc for new language additions [7] (deferred to Nov 29)
  • Add networking-cisco back into the Big Tent [8] (deferred until dhellmann files proposal for driver-only teams)
  • Storlets to become official - Proposed governance change [9] (missing items tracking at [10])
  • Equal Integration Chances for all Projects [11] (needs round 2)


Apologies for Absence

  • sdague


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