OpenStack Technical Committee¶
The OpenStack Technical Committee is the governing body of the OpenStack open source project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters. This includes developers, operators and end users of the software.
The Technical Committee is formally defined in the OpenStack Foundation bylaws (in particular article 4.1(b), article 4.13 and Appendix 4) and further refined in the OpenStack Technical Committee Charter.
Work under the Technical Committee is organized under official OpenStack Project Teams (responsible for the production of the software up to release), Special Interest Groups (SIGs) (groups working to advance a particular facet of OpenStack), Popup teams (formed around a limited cross-project objective) and Working groups (delegations from the TC to fill specific functions like election organization).
These pages contain OpenStack Technical Committee reference documents and track official resolutions voted by the committee.
Current Members¶
Full Name |
IRC |
Elected On |
Role |
|
|---|---|---|---|---|
Ghanshyam Mann |
gmann |
gmann@ghanshyammann.com |
September 2023 |
|
Dan Smith |
dansmith |
dms@danplanet.com |
September 2023 |
|
Jay Faulkner |
JayF |
jay@jvf.cc |
September 2023 |
|
Sławek Kapłoński |
slaweq |
skaplons@redhat.com |
February 2023 |
|
Kristi Nikolla |
knikolla |
knikolla@bu.edu |
February 2023 |
|
Brian Rosmaita |
rosmaita |
rosmaita.fossdev@gmail.com |
February 2023 |
|
Amy Marrich |
spotz |
amy@demarco.com |
February 2023 |
|
James Page |
jamespage |
james.page@ubuntu.com |
February 2023 |
|
Jens Harbott |
frickler |
frickler@offenerstapel.de |
September 2023 |
Reference documents and Resolutions¶
- Reference documents
- The Four Opens
- Guiding Principles
- OpenStack Technical Committee Charter
- OpenStack Project Teams
- Popup teams
- Vision for OpenStack Clouds
- Upstream Investment Opportunities
- Role of the OpenStack Technical Committee
- Requirements for new OpenStack Project applications
- Requirements for language additions to the OpenStack Ecosystem
- Guidelines for dropping project teams from OpenStack governance
- Licensing requirements
- Base services
- OpenStack User Committee Charter
- Working groups
- Service and Project Naming
- Project Testing Interface
- IRC Channel Policies
- Release Identification/Name
- Tags
- Requirements for previously-used incubation/integration process
- House rules for governance changes approval
- Comparison of Official Group Structures
- Technical Committee Onboarding Guide
- Handling the OpenStack name in external services
- TC and PTL Elections exceptions
- TC Chair Election Process
- Emerging and inactive projects
- OpenStack-wide Goals
- Resolutions
- 2023-07-24 Unmaintained status replaces Extended Maintenance
- 2022-09-27 Dedicate Zed Release to Ilya Etingof
- 2022-05-24 OpenStack release identification process
- 2022-04-14 Drop Lower Constraints Maintenance
- 2022-02-10 Release Cadence Adjustment
- 2021-12-24 Removal of the tags framework
- 2021-09-23 Stable Core Team Process
- 2021-06-02 ‘OpenStack ATC’ definition
- 2021-05-26 The OpenStack community IRC network moving to OFTC
- 2020-10-28 OpenStackClient TC Policy
- 2020-09-20 ‘OpenStack TC approved release’ definition
- 2020-08-31 Reinstate weekly meetings
- 2020-08-03 Distributed Project Leadership
- 2020-02-28 OpenStack-Infra split to OpenDev
- 2019-07-11 Mandatory Repository Retirement
- 2019-03-22 Namespace Unofficial Projects
- 2018-10-24 Python Update Process
- 2018-10-18 T Release Name
- 2018-05-29 Python2 Deprecation Timeline
- 2018-03-19 SIG Governance
- 2018-03-07 Location of tempest tests for OpenStack Trademark Programs
- 2018-03-01 Extended maintenance for stable branches
- 2018-02-15 Use of OpenStack CI Resources for External Projects
- 2018-02-06 Dedicate Queens Release to Shawn Pearce
- 2017-07-18 Allow for meetings to happen outside meeting channels
- 2017-06-20 Definition of Upstream Support
- 2017-06-13 Document current level of community database support
- 2017-05-30 Guidelines for Managing Releases of Binary Artifacts
- Technical Committee Vision for 2019 (Drafted April, 2017)
- 2017-03-29 Use case for the addition of Go as a supported language
- 2017-03-17 OpenStack and Cloud Applications
- 2016-07-05 Stewardship Working Group (SWG)
- 2016-05-04 Recommendation on API Proxy Tests for DefCore
- 2016-04-14 Grant Cross-Project Team Voting in CP Specifications
- 2016-02-17 OpenStack Mission amendment
- 2016-01-19 Stackforge Namespace Retirement
- 2015-12-11 Compute Requirements for Images and Kernels
- 2015-09-01 OpenStack Programming Languages
- 2015-05-12 Acknowledging use of UTC
- 2014-12-02 OpenStack project structure reform specification
- 2014-11-28 Process for Leaderless Programs
- 2014-09-09 Recommendation to Adopt DCO as CLA
- 2014-07-11 Election Activities
- 2014-06-17 DefCore Capabilities Scoring
- 2014-04-02 DefCore Designated Sections Guidelines
- 2014-02-11 DefCore Response
- 2013-31-06 Ceilometer and Heat Official Names
- Superseded Resolutions
Meeting¶
Beyond discussing on the mailing-list and participating in ad-hoc IRC meetings, TC members will hold meeting at the following time every week:
You can contact TC members at any time, but there will be an effort to be present at those specific hours. So don’t hesitate to reach out if you have any question!
How to propose governance changes¶
Motions should be posted for discussion as a proposed change to the openstack/governance repository (on review.opendev.org) and/or as a “[tc]” thread to the openstack-discuss@lists.openstack.org mailing-list. Upon verification, the chair will put the motion on the current proposals tracker.
We use Gerrit to record votes, so before being formally voted on or approved, motions will have to be presented as a change in the openstack/governance git repository. You can find instructions on how to do that in the Developer’s guide section of the Infra manual. Please contact the TC chair in case you need help. Note that a number of simpler changes do not require formal voting by the majority of the Technical Committee membership. Those exceptions are listed in the House rules for governance changes approval document.
Summary of User Survey Questions Responses¶
Since 2019 the OpenStack Technical Committee has added questions to the annual OpenStack User Survey. Below are links to summaries and analysis of those responses.
