Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 16: Line 16:
 
* Let projects add repos without prior-approval [https://review.openstack.org/173465]
 
* Let projects add repos without prior-approval [https://review.openstack.org/173465]
 
* Projects list housekeeping
 
* Projects list housekeeping
** Use lower case service in Mistral [https://review.openstack.org/173501]
 
 
** Add glean to infra [https://review.openstack.org/172748]
 
** Add glean to infra [https://review.openstack.org/172748]
** Do not capitalize 'Service' in the service name of Magnum [https://review.openstack.org/173294]
 
** Add 'regulatory' to congress service name [https://review.openstack.org/169480]
 
 
** Rename keystoneclient-federation to saml2 [https://review.openstack.org/173619]
 
** Rename keystoneclient-federation to saml2 [https://review.openstack.org/173619]
 
** Add django-openstack-auth-kerberos project [https://review.openstack.org/172802]
 
** Add django-openstack-auth-kerberos project [https://review.openstack.org/172802]
 
** Changes Rally to Benchmark service to better match other names [https://review.openstack.org/173308]
 
** Changes Rally to Benchmark service to better match other names [https://review.openstack.org/173308]
 
* Governance repo housekeeping
 
* Governance repo housekeeping
 +
** Update sphinx docs to support team based tags [https://review.openstack.org/172591]
 +
** Remove unused code from teams.py [https://review.openstack.org/172592]
 
** Update formatting of teams page [https://review.openstack.org/172593]
 
** Update formatting of teams page [https://review.openstack.org/172593]
** Remove unused code from teams.py [https://review.openstack.org/172592]
+
** Update diversity.py to use projects.yaml [https://review.openstack.org/174023]
 +
** Add tool/framework to automatically validate the tag applications. [https://review.openstack.org/174024]
 +
** Add check for 'release:has-stable-branches' [https://review.openstack.org/174169]
 
* Open discussion
 
* Open discussion
 
** Cross-project track at the Design Summit [https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing]
 
** Cross-project track at the Design Summit [https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit?usp=sharing]
Line 33: Line 34:
 
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:
  
* WIP - Add Group Based Policy Project [https://review.openstack.org/161902]
+
* Add 'regulatory' to congress service name [https://review.openstack.org/169480] (pending progress on approval)
* WIP: Add reference to running an election to new projects requirements [https://review.openstack.org/162789]
+
* Adding the Chef cookbooks to OpenStack [https://review.openstack.org/175000] (planned Apr 27)
* WIP - add some tags describing roles [https://review.openstack.org/163236]
+
* Updated based on PTL elections [https://review.openstack.org/175007] (needs election officials +1)
 +
* WIP - Add Group Based Policy Project [https://review.openstack.org/161902] (marked WIP)
 +
* WIP: Add reference to running an election to new projects requirements [https://review.openstack.org/162789] (marked WIP)
 +
* WIP - add some tags describing roles [https://review.openstack.org/163236] (marked WIP)
  
  

Revision as of 11:38, 20 April 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

  • April 21st, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


Agenda

  • Adding MagnetoDB to OpenStack [1]
  • Adding the Puppet modules to OpenStack [2]
  • Let projects add repos without prior-approval [3]
  • Projects list housekeeping
    • Add glean to infra [4]
    • Rename keystoneclient-federation to saml2 [5]
    • Add django-openstack-auth-kerberos project [6]
    • Changes Rally to Benchmark service to better match other names [7]
  • Governance repo housekeeping
    • Update sphinx docs to support team based tags [8]
    • Remove unused code from teams.py [9]
    • Update formatting of teams page [10]
    • Update diversity.py to use projects.yaml [11]
    • Add tool/framework to automatically validate the tag applications. [12]
    • Add check for 'release:has-stable-branches' [13]
  • Open discussion
    • Cross-project track at the Design Summit [14]


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 'regulatory' to congress service name [15] (pending progress on approval)
  • Adding the Chef cookbooks to OpenStack [16] (planned Apr 27)
  • Updated based on PTL elections [17] (needs election officials +1)
  • WIP - Add Group Based Policy Project [18] (marked WIP)
  • WIP: Add reference to running an election to new projects requirements [19] (marked WIP)
  • WIP - add some tags describing roles [20] (marked WIP)


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