2e93447e66
Per the past year of discussions, culminating in the most recent mailing list thread[*], it's apparent that providing a consistent solution for storage of key material and similar secrets by security features of various OpenStack services is in the best interests of the project. By providing this guarantee in the base services set, projects don't need to worry about implementing insecure fallback alternatives or needlessly duplicating functionality to cope with the lack of an already-available solution. [*] http://lists.openstack.org/pipermail/openstack-dev/2018-May/130567.html Change-Id: Ia46211f41726d5671bf28a632d17fc56965b6fcc
This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
- goals/
Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.