Difference between revisions of "Meetings/TechnicalCommittee"
(→Agenda) |
|||
Line 16: | Line 16: | ||
* Adding Rally to OpenStack [https://review.openstack.org/169357] | * Adding Rally to OpenStack [https://review.openstack.org/169357] | ||
* Adding the security team. [https://review.openstack.org/170172] | * Adding the security team. [https://review.openstack.org/170172] | ||
− | |||
* Tags | * Tags | ||
** Apply the team:diverse-affiliation tag [https://review.openstack.org/168968] | ** Apply the team:diverse-affiliation tag [https://review.openstack.org/168968] | ||
Line 28: | Line 27: | ||
** Add 'regulatory' to congress service name [https://review.openstack.org/169480] | ** Add 'regulatory' to congress service name [https://review.openstack.org/169480] | ||
* 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 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 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: 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] | * WIP: 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 39: | Line 41: | ||
* tbd | * tbd | ||
+ | |||
=== Presenting a motion before the TC === | === Presenting a motion before the TC === |
Revision as of 09:21, 3 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 7th, 20:00 UTC
- Chair: Thierry Carrez (ttx)
Agenda
- Give project teams still under consideration by April 10 a derogation to be at the Design Summit
- Defcore process [1] discussion
- Adding Rally to OpenStack [2]
- Adding the security team. [3]
- Tags
- Adds the openstack/os-cloud-management to TripleO... [8]
- Projects list housekeeping
- 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:
- Adding Mistral Workflow Service to OpenStack [12]
- WIP - Add Group Based Policy Project [13]
- WIP: Add reference to running an election to new projects requirements [14]
- WIP: Need guidance for docs.openstack.org publishing and brand guidelines, especially for newest projects [15]
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