Difference between revisions of "Meetings/TechnicalCommittee"
| Line 16: | Line 16: | ||
** Definition of the release:* tags [https://review.openstack.org/157322] | ** Definition of the release:* tags [https://review.openstack.org/157322] | ||
** Next WIP tags [http://ttx.re/facets-of-the-integrated-release.html] [https://review.openstack.org/163851] [https://review.openstack.org/163236] | ** Next WIP tags [http://ttx.re/facets-of-the-integrated-release.html] [https://review.openstack.org/163851] [https://review.openstack.org/163236] | ||
| + | ** Moving tags to a separate project-catalog repository (to make it clear it's more documentation than governance) | ||
* New project teams additions | * New project teams additions | ||
** Freezing or slowly considering [http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html] | ** Freezing or slowly considering [http://lists.openstack.org/pipermail/openstack-dev/2015-March/058689.html] | ||
| − | |||
** Add OpenStackClient project [https://review.openstack.org/161885] | ** Add OpenStackClient project [https://review.openstack.org/161885] | ||
| − | |||
* Other governance changes | * Other governance changes | ||
| − | |||
** Add the new developer-reference repo to the TC list [https://review.openstack.org/161451] | ** Add the new developer-reference repo to the TC list [https://review.openstack.org/161451] | ||
** Add reference to running an election to new projects requirements [https://review.openstack.org/162789] | ** Add reference to running an election to new projects requirements [https://review.openstack.org/162789] | ||
| Line 32: | Line 30: | ||
** Add Gnocchi repository to Ceilometer [https://review.openstack.org/162145] | ** Add Gnocchi repository to Ceilometer [https://review.openstack.org/162145] | ||
** Add new project puppet-openstackci to infra [https://review.openstack.org/163246] | ** Add new project puppet-openstackci to infra [https://review.openstack.org/163246] | ||
| − | |||
* Open discussion | * Open discussion | ||
| Line 39: | Line 36: | ||
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: | ||
| − | * | + | * Magnum - OpenStack Containers Service [https://review.openstack.org/161080] (planned March 24) |
| + | * Adding the Murano Application Catalog to OpenStack [https://review.openstack.org/162745] | ||
Revision as of 15:28, 13 March 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
- March 17th, 20:00 UTC
- Chair: Thierry Carrez (ttx)
Agenda
- Final rubberstamping of "Cross-Project spec to eliminate SQL Schema Downgrades" [1]
- Tags
- New project teams additions
- Other governance changes
- 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:
- Magnum - OpenStack Containers Service [16] (planned March 24)
- Adding the Murano Application Catalog to OpenStack [17]
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
