Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

Line 6: Line 6:
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* April 7th, 20:00 UTC
+
* April 14th, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
* Chair: Thierry Carrez (ttx)
  
Line 12: Line 12:
 
==== Agenda ====
 
==== Agenda ====
  
* Give project teams still under consideration by April 10 a derogation to be at the Design Summit
+
* Adding Mistral Workflow Service to OpenStack [https://review.openstack.org/170225]
* Defcore process [http://git.openstack.org/cgit/openstack/defcore/tree/process/2015A.rst] discussion
+
* tbd
* Adding Rally to OpenStack [https://review.openstack.org/169357]
+
* More Defcore process [http://git.openstack.org/cgit/openstack/defcore/tree/process/2015A.rst] discussion
* Adding the security team. [https://review.openstack.org/170172]
 
* Tags
 
** Apply the team:diverse-affiliation tag [https://review.openstack.org/168968]
 
** Add a two-organization rule to the diverse-affiliation tag [https://review.openstack.org/168969]
 
** Add diversity helper script [https://review.openstack.org/168970]
 
** Add "release:has-stable-branches" tag [https://review.openstack.org/169777]
 
 
* Projects list housekeeping
 
* Projects list housekeeping
** Adds openstack/tripleo-common to TripleO... [https://review.openstack.org/166723]
+
** tbd
** Add new project puppet-pgsql_backup to infra [https://review.openstack.org/168117]
 
** Update wording for Murano mission [https://review.openstack.org/168299]
 
** Add 'regulatory' to congress service name [https://review.openstack.org/169480]
 
 
* Open discussion
 
* Open discussion
** Need guidance for docs.openstack.org publishing and brand guidelines, especially for newest projects [http://lists.openstack.org/pipermail/legal-discuss/2015-March/000356.html]
 
  
  
Line 33: Line 23:
 
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:
  
* Adding Mistral Workflow Service to OpenStack [https://review.openstack.org/170225]
 
 
* 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]
 
* WIP - add some tags describing roles [https://review.openstack.org/163236]
 
* WIP - add some tags describing roles [https://review.openstack.org/163236]
* Add openstack-dev/specs-cookiecutter [https://review.openstack.org/170946]
 
* Adopt openstack/ossa by Release cycle management [https://review.openstack.org/168814]
 
  
  

Revision as of 08:30, 8 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 14th, 20:00 UTC
  • Chair: Thierry Carrez (ttx)


Agenda

  • Adding Mistral Workflow Service to OpenStack [1]
  • tbd
  • More Defcore process [2] discussion
  • Projects list housekeeping
    • 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 [3]
  • WIP: Add reference to running an election to new projects requirements [4]
  • WIP - add some tags describing roles [5]


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