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 TC governance website at https://governance.openstack.org/tc/ . It meets weekly in an open meeting in the
#openstack-meeting IRC channel on Freenode.
- April 25th, 20:00 UTC
- Chair: Doug Hellmann (dhellmann)
- Welcome new membership
- Adjustments to status:maintenance-mode tag definition 
- Presentation of User Survey findings (heidijoy - email@example.com)
- See a 4-minute video overview of report highlights
- Download the full User Survey report
- Analyze data yourself with six global filters
- Key findings for the TC:
- Report represents 44% more deployments (nearly 600) and 22% more organizations than ever before, however, fewer total respondents
- The majority of OpenStack users are on an unsupported release: all deployments / deployments in production
- NPS scores declined for users overall and for those with deployments - see the full report for verbatim comments
- 12 projects asked specific questions to inform future development. See answers on pages 58-65 of the report.
- See the report "Deployment Decisions" section (pages 42-57) for installation/configuration insights.
- Update diversity tags 
- Next steps (if any) for Driver teams   and networking-cisco's standing request 
- Abandoning the weekly meeting (flaper87)
- 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:
- Describe what upstream support means  (might be unnecessary if we decide to contract for technical reasons)
- Add Queens goal split out tempest plugins  (work in progress)
- deprecate postgresql in OpenStack  (needs clarity about whether we would drop it even if we received support, forum discussion)
- assert:supports-api-compatibility tag  (pending API change guidelines update )
- Draft technical committee vision for public feedback  (waiting for feedback)
- Fix comment about design summits  (waiting for new revision)
Apologies for Absence
- Thierry Carrez (April 25th)
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