Tony Breeds 73f0b8c897 Switch requirements to distributed leadership
The purpose of this change is to make it explicit that "team leadership"
for the requirements team is equally shared between the 2 named
individuals.  While this is more of a co-PTL model we're leveraging the
distibuted team leadership model adopted by the TC resolution[1]

[1] https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html

Change-Id: Ib6c4c4f4a45f42e4daaa910cd728f946e72ff75c
2022-08-25 20:04:39 -07:00
2022-04-20 20:38:40 -05:00
2019-05-22 22:02:02 +08:00
2019-04-19 19:47:56 +00:00
2022-08-08 19:36:21 +02:00
2022-04-20 20:38:40 -05:00
2021-09-16 15:58:18 +00:00
2021-01-07 10:49:37 +01:00

openstack-governance

The repository https://opendev.org/openstack/governance/ contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee. It also contains a library for accessing some of the machine-readable data in the repository.

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://governance.openstack.org/tc/ for details.

Description
OpenStack Technical Committee Decisions
Readme 42 MiB
Languages
Python 95.3%
DIGITAL Command Language 3.5%
Shell 1%
C++ 0.2%