openstack/governance-sigs
Code Issues Proposed changes
master
governance-sigs/doc/source/index.rst
ricolin 43c6abee39 Update retire SIG process 
Allow retire a non-finish SIG
* add archived-sigs.yaml to collect SIGs consider retired but didn't
  finish it's mission.
* Update documentation
* Add status `completed` and `archived` to SIG.
* Add `reason` field to SIG
* Show retired SIGs in index page

Change-Id: I6e5f35aa093340d6e553fe52c6ffe9061bc9191b
2021-03-26 19:33:18 +08:00

1.2 KiB
Raw Permalink Blame History

OpenStack SIGs

The OpenStack SIGs (Special Interest Groups) are a form of working group in OpenStack that is not directly responsible for producing a part of the OpenStack software release. As such, they do not require the same level of accountability that project teams do.

SIGs are a good match for an activity that centers around a topic or practice that spans all the community (developers, operators, end users...), by forming a guild of people with a shared interest.

SIGs can own code repositories and produce software (independently of the OpenStack software release itself). Contributions to a SIG grant voting rights for the Technical Committee elections, in the same way contributing to an OpenStack project team does.

tact-sig

reference/sig-guideline

Retired SIGs

Archived SIGs

These SIGs are retired but have not yet completed their mission.

Completed SIGs

These SIGs are retired and have completed their mission.