summaryrefslogtreecommitdiff
path: root/governance.md
diff options
context:
space:
mode:
authorMichelle Noorali <michelle@deis.com>2016-12-09 14:08:15 -0500
committerMichelle Noorali <michelle@deis.com>2016-12-09 14:09:56 -0500
commit577c94feea34f755dc67c8f70ecdc61554f98b1f (patch)
treed910e4ab724e268d3d5d15dbd1274d41615f071a /governance.md
parentab32d77a39d10558d752be52342951a59519e0a7 (diff)
add sig governance doc
Diffstat (limited to 'governance.md')
-rw-r--r--governance.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/governance.md b/governance.md
new file mode 100644
index 00000000..d6f63bb2
--- /dev/null
+++ b/governance.md
@@ -0,0 +1,12 @@
+# Kubernetes SIG Governance
+
+In order to standardize Special Interest Group efforts, create maximum transparency, and route contributors to the appropriate SIG, SIGs should follow the guidelines stated below:
+
+* Meet regularly, at least for 30 minutes every 3 weeks, except November and December
+* Keep up-to-date meeting notes, linked from the SIG's page in the community repo
+* Announce meeting agenda and minutes after each meeting, on their SIG mailing list
+* Record SIG meeting and make it publicly available
+* Ensure the SIG's mailing list and slack channel are archived
+* Report activity in the weekly community meeting at least once every 6 weeks
+* Participate in release planning meetings and retrospectives, and burndown meetings, as needed
+* Ensure related work happens in a project-owned github org and repository, with code and tests explicitly owned and supported by the SIG, including issue triage, PR reviews, test-failure response, bug fixes, etc.