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.
- July 14th, 20:00 UTC
- Chair: Thierry Carrez (ttx)
- Redefine release tags to match new models  (pending new patchset)
- Add Fuel to OpenStack Projects 
- Add neutron to starter-kit:compute  (pending new patchset)
- Workgroup reports
- Open discussion
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:
- Add Stackforge Retirement resolution  (pending new patchset)
- Fix typo to 'Bare metal service'  (agentle driving it, likely to be abandoned)
- Adds Debian & derivatives packaging to OpenStack  (pending narrowing of scope to Debian-only)
- RPM distribution packaging of OpenStack  (pending progress on team formation)
- Ironic is considering changing their release cycle  (pending spec at https://review.openstack.org/#/c/185171/)
- Add Compass to OpenStack Projects  (learning more of the OpenStack Way)
- [WIP] Add Akanda to OpenStack Projects List  (marked WIP)
- WIP - Add Group Based Policy Project  (marked WIP)
- WIP - add some tags describing roles  (marked WIP)
Apologies for Absence
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 firstname.lastname@example.org, with a pointer to that thread should be posted to email@example.com 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