summaryrefslogtreecommitdiff
path: root/communication
diff options
context:
space:
mode:
authorJorge O. Castro <jorge.castro@gmail.com>2018-05-10 11:40:44 -0400
committerJorge O. Castro <jorge.castro@gmail.com>2018-05-10 11:40:44 -0400
commit630192f8cf6318c16f46e21569ea290bc38b7223 (patch)
treef9210d96b63ef28c7d3b3ab7a0a92bba00a7c19f /communication
parentd69433890351f7a249ea0f1e52ad2711656a0f32 (diff)
Explicitly list the steering committee as the final escalation point
Diffstat (limited to 'communication')
-rw-r--r--communication/moderation.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/communication/moderation.md b/communication/moderation.md
index 481ff6ec..be35abe8 100644
--- a/communication/moderation.md
+++ b/communication/moderation.md
@@ -28,6 +28,10 @@ Moderators _SHOULD_:
- Help your colleagues if you recognize them in one of the [stages of burnout](https://opensource.com/business/15/12/avoid-burnout-live-happy).
- Be helpful and have fun!
+## Violations
+
+The Kubernetes [Steering Committee](https://github.com/kubernetes/steering) will have the final authority regarding escalated moderation matters. Violations of the Code of Conduct will be handled on a case by case basis. Depending on severity this can range up to and including removal of the person from the community, though this is extremely rare.
+
## Specific Guidelines
These guidelines are for tool-specific policies that don't fit under a general umbrella.