openstack
/
governance-sigs
Code Issues Proposed changes

Improve SIG intro 

Remove mentions of governance bodies, as it's now a bit confusing
(SIGs being under the TC+UC body).

Be more explicit about the difference between a project team and
a SIG.

Change-Id: I7cf8f2b5ae0131d5226c3284665ce492a7e72336
This commit is contained in:
Thierry Carrez 2020-08-12 17:29:42 +02:00
parent 38a0b352b5
commit 6ad5d54f49
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/index.rst
View File

@ -3,13 +3,20 @@
================
The OpenStack SIGs (Special Interest Groups) are a form of
working group in OpenStack that is an emanation of the community
as a whole and is not directly tied to a specific governance body.
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.
.. sigtable::
:datafile: ../../sigs.yaml