Ghanshyam Mann 340683abcb Changing new release cadence name
With the outcome of the legal check, it is not clear to us
that tick tock words are ok to use for our new release
cadence arrangement and in what form.

In TC, we decided to use a different name and 'SLURP'
is the choice of the majority[1]

Let's update our resolution document to reflect the new name
and I am adding a "communication" section to explain that how
we will use "SLURP" in our documentation.

[1] https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html#l-191

Change-Id: If82240c1f62842314b48caa4694280c0be147919
2022-05-16 10:48:18 -05:00
2022-04-20 20:38:40 -05: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-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%