You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: communication/moderation.md
+49-29Lines changed: 49 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,11 @@
1
+
---
2
+
title: "Moderation Rules and Responsibilities"
3
+
description: |
4
+
Overview of community property moderator roles, responsibilities, selection,
5
+
and best practices.
6
+
---
7
+
8
+
<!-- omit in toc -->
1
9
# Moderation on Kubernetes Communications Channels
2
10
3
11
@@ -12,20 +20,21 @@ lists, YouTube, Zoom, and any property listed in the SIG Contributor Experience
12
20
13
21
---
14
22
15
-
-[Moderation on Kubernetes Communications Channels](#moderation-on-kubernetes-communications-channels)
16
-
-[Selection of Moderators](#selection-of-moderators)
17
-
-[Moderators Pro Tempore](#moderators-pro-tempore)
18
-
-[Rotation of Moderators](#rotation-of-moderators)
19
-
-[Roles and Responsibilities](#roles-and-responsibilities)
20
-
-[Violations](#violations)
21
-
-[Escalation Procedures](#escalation-procedures)
22
-
-[Platform Specific Guidelines](#platform-specific-guidelines)
23
-
-[Discuss](#discuss)
24
-
-[Mailing List](#mailing-list)
25
-
-[Slack](#slack)
26
-
-[YouTube](#youtube)
27
-
-[Zoom](#zoom)
28
-
-[References and Resources](#references-and-resources)
23
+
24
+
-[Selection of Moderators](#selection-of-moderators)
25
+
-[Moderators Pro Tempore](#moderators-pro-tempore)
26
+
-[Rotation of Moderators](#rotation-of-moderators)
27
+
-[Roles and Responsibilities](#roles-and-responsibilities)
28
+
-[Violations](#violations)
29
+
-[Escalation Procedures](#escalation-procedures)
30
+
-[Platform Specific Guidelines](#platform-specific-guidelines)
31
+
-[Discuss](#discuss)
32
+
-[Mailing List](#mailing-list)
33
+
-[Slack](#slack)
34
+
-[YouTube](#youtube)
35
+
-[Zoom](#zoom)
36
+
-[Process for Adding a Moderator](#process-for-adding-a-moderator)
37
+
-[References and Resources](#references-and-resources)
29
38
30
39
---
31
40
@@ -64,8 +73,7 @@ The process for applying for moderatorship is as follows:
64
73
using to moderate.
65
74
-**[Open an issue][moderator request] against the kubernetes/community repo**
66
75
- Ensure your sponsors are @mentioned on the issue.
67
-
- Complete every item on the checklist ([preview the current version of the
68
-
template][moderator template])
76
+
- Complete every item on the checklist
69
77
- Make sure that the list of contributions included is representative of your
70
78
work on the project.
71
79
- Have your sponsoring reviewers reply confirmation of sponsorship: `+1` or
@@ -116,9 +124,12 @@ Moderators _MUST_:
116
124
- Abide by the documented tasks and actions required of moderators.
117
125
- Ensure that the Kubernetes [Code of Conduct] is in effect on all official
118
126
Kubernetes communication channels.
119
-
- Make yourself generally available during working hours in your time zone for moderation.
120
-
- This can be handled as a group so that there is enough coverage of people to allow for absences/travel.
121
-
- Ensure you are on #slack-admins during work hours and notifications are set appropriately.
127
+
- Make yourself generally available during working hours in your time zone for
128
+
moderation.
129
+
- This can be handled as a group so that there is enough coverage of people to
130
+
allow for absences/travel.
131
+
- Ensure you are on #slack-admins during work hours and notifications are set
132
+
appropriately.
122
133
- Become familiar with the [Kubernetes Community Values].
123
134
- Take care of spam as soon as possible, which may mean taking action by
124
135
removing a member from that resource.
@@ -173,10 +184,10 @@ procedures:
173
184
other primary moderators as soon as possible.
174
185
- If appropriate, the next level of people to contact are the OWNERS of the
175
186
subproject.
176
-
- If appropriate, the next level of people to contact is the[Code of Conduct
177
-
Committee].
178
-
- If appropriate, the next level of people to contact is the[Steering
179
-
Committee].
187
+
- If appropriate, the next level of people to contact is the
188
+
[Code of Conduct Committee].
189
+
- If appropriate, the next level of people to contact is the
190
+
[Steering Committee].
180
191
- Moderators will have access to a private document with contact information of
181
192
the appropriate people.
182
193
- Primary moderators will then execute an audit of the affected property:
@@ -227,12 +238,22 @@ This is the workflow for adding a moderator.
227
238
- Moderator applies by [filing an issue] in the kubernetes/community repo
228
239
- Moderator gets approval from 2 current moderators
229
240
- Add the person to their respective moderation tool:
230
-
- Slack - Add them as a slack workspace admins (instructions pinned on #slack-admins-private): Invite them to #slack-admins-private, #slack-admins, #slack-log, #slack-reports and #slack-invites
241
+
- Slack - Add them as a slack workspace admins (instructions pinned on
242
+
#slack-admins-private): Invite them to #slack-admins-private, #slack-admins,
243
+
#slack-log, #slack-reports and #slack-invites
231
244
- Discuss - Change their permission to moderator
232
-
- Kubernetes.io Google group - PR the person into the correct yaml file in kubernetes/k8s.io. (Note: This only applies to groups using @kubernetes.io, most other lists are still managed out of band)
233
-
- Ensure they add that they are an admin in their profile page on whatever service they are administrating
234
-
- Add them to the moderators mailing list by PRing them into this file, ensure you link to the person's moderator github application as part of the PR for reference: https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml
235
-
- Ensure person is enrolled for a future bias training course, this can either be provided by the project or their employer.
245
+
- Kubernetes.io Google group - PR the person into the correct yaml file in
246
+
kubernetes/k8s.io. (Note: This only applies to groups using @kubernetes.io,
247
+
most other lists are still managed out of band)
248
+
- Ensure they add that they are an admin in their profile page on whatever
249
+
service they are administrating
250
+
- Add them to the moderators mailing list by PRing them into the
[filing an issue]: https://github.com/kubernetes/community/issues/new/?assignees=&labels=area%2Fcommunity-management%2C+sig%2Fcontributor-experience&template=moderator_application.md&title=REQUEST%3A+New+moderator+for+%3Cyour-GH-handle%3E+of+%3Ck8s+property%3E
0 commit comments