Content about SIGs on governance.o.o
709a567071
Reorganize and simplify SIG guidelines, so that creating and operating a SIG does not seem so daunting. In particular: - Remove redundant information (like the definition of a SIG) and generally be more concise - Regroup SIG lifecycle guidelines (creating, updating, retiring) in the same chapter rather than spread it out across all the document - Be generally less prescriptive and more on the 'best practices' side - Mention SIG statuses as part of the SIG lifecycle guidelines, rather that on its own separate document - Remove the "completed" status which is redundant with the presence in the completed-sigs.yaml file Change-Id: Id1a754512f08bed55926dd7b65916c1f42fb446f |
||
---|---|---|
doc/source | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
completed-sigs.yaml | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
sigs.yaml | ||
test-requirements.txt | ||
tox.ini |
This repository contains information about OpenStack SIGs.