openstack/governance
Code Issues Proposed changes
28cc944d53
governance/resolutions/20180319-sig-governance.rst
Jeremy Stanley b94da111e7 Reverse sort order for resolution date globs 
Sphinx 1.5 and later allows a :reversed: parameter for :glob:
toctrees. Since we're presenting our resolution index in reverse
chronological order grouped by year, reversing the glob order keeps
the dates within each year consistently ordered as well. Yes, this
is probably me being OCD.

The SIGs governance resolution file was inconsistently named,
leading to it showing up outside the expected sort order. Rename the
file and add a permanent redirect from the old URL to the new one.

Related cleanup, the main index toctree was incorrectly marked as a
:glob: even though it didn't use any wildcard patterns so has been
corrected.

Change-Id: Ifbc6db87e41f01311b430080b97154d01708a2d4
2018-10-05 16:44:07 +00:00

871 B
Raw Blame History

2018-03-19 SIG Governance

OpenStack SIGs need a minimal governance structure to make final calls in case conflicts between SIGs or within the leadership of a given SIG cannot be solved at the SIG level.

This resolution states that such conflicts should be escalated to the SIG admins group for resolution.

The SIG admins group is formed of one User Committee representative and one Technical Committee representative. In case the two SIG admins disagree on the resolution of the conflict, the OpenStack Foundation Executive Director will be asked to break the tie.

NB: the SIG admins group also has +2A rights on the governance-sigs repository (source of the SIG governance website), and therefore finally approves new SIG submissions.