Go to file
Dmitriy Rabotyagov ec288509da Remove Freezer from inactive state
This patch proposes to re-establish a Freezer as Active project. During
inactivity following issues were addressed:

* CI health recovered for remaining repositories [1][2][3][4][5]
* Proposed to retire freezer-dr project to focus on main project objective [6]
* Re-established access to #openstack-freezer IRC channel
* Slightly updated docs to include more necessary infromation about
the project for potential users

There are still ongoing activities to fuly put back project back on
rails, like moving bug tracker back to launchpad [7], though given that
we've passed a milestone-2, where clients should be released [8],
it's already time to decide if Epoxy should be considered as a release
for marking Freezer as active project again.

[1] https://review.opendev.org/q/project:openstack/freezer
[2] https://review.opendev.org/q/project:openstack/freezer-api
[3] https://review.opendev.org/q/project:openstack/python-freezerclient
[4] https://review.opendev.org/q/project:openstack/freezer-tempest-plugin
[5] https://review.opendev.org/q/project:openstack/freezer-web-ui
[6] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3VQUSJHBOOH3MKIMHUINNV75REF3GS7Z/
[7] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/7PD7TVDLSHVXL7O7HFDVQXAZVW2EUV4G/
[8] https://review.opendev.org/c/openstack/releases/+/938780

Change-Id: Ib34b6f91cfd6134e695b768fbbac226b930017ad
2025-01-10 17:55:20 +01:00
2024-11-21 10:36:14 -08:00
2019-05-22 22:02:02 +08:00
2019-04-19 19:47:56 +00:00
2023-09-06 10:09:30 +02:00
2024-02-19 02:52:10 +09:00
2023-04-21 12:42:44 -07:00
2023-09-06 10:09:30 +02: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 45 MiB
Languages
Python 88.7%
DIGITAL Command Language 5.8%
Shell 5.3%
C++ 0.2%