Skip to content

Commit 3a32d60

Browse files
committed
Add Hugo metadata and update moderator procedure
1 parent 43a563c commit 3a32d60

File tree

1 file changed

+49
-29
lines changed

1 file changed

+49
-29
lines changed

communication/moderation.md

Lines changed: 49 additions & 29 deletions
Original file line numberDiff line numberDiff 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 -->
19
# Moderation on Kubernetes Communications Channels
210

311

@@ -12,20 +20,21 @@ lists, YouTube, Zoom, and any property listed in the SIG Contributor Experience
1220

1321
---
1422

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)
2938

3039
---
3140

@@ -64,8 +73,7 @@ The process for applying for moderatorship is as follows:
6473
using to moderate.
6574
- **[Open an issue][moderator request] against the kubernetes/community repo**
6675
- 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
6977
- Make sure that the list of contributions included is representative of your
7078
work on the project.
7179
- Have your sponsoring reviewers reply confirmation of sponsorship: `+1` or
@@ -116,9 +124,12 @@ Moderators _MUST_:
116124
- Abide by the documented tasks and actions required of moderators.
117125
- Ensure that the Kubernetes [Code of Conduct] is in effect on all official
118126
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.
122133
- Become familiar with the [Kubernetes Community Values].
123134
- Take care of spam as soon as possible, which may mean taking action by
124135
removing a member from that resource.
@@ -173,10 +184,10 @@ procedures:
173184
other primary moderators as soon as possible.
174185
- If appropriate, the next level of people to contact are the OWNERS of the
175186
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].
180191
- Moderators will have access to a private document with contact information of
181192
the appropriate people.
182193
- Primary moderators will then execute an audit of the affected property:
@@ -227,12 +238,22 @@ This is the workflow for adding a moderator.
227238
- Moderator applies by [filing an issue] in the kubernetes/community repo
228239
- Moderator gets approval from 2 current moderators
229240
- 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
231244
- 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
251+
[[email protected] group] linking to the person's moderator github
252+
application as part of the PR.
253+
- Ensure person is enrolled for a future bias training course, this can either
254+
be provided by the project or their employer.
255+
256+
[[email protected] group]: https://github.com/kubernetes/k8s.io/blob/master/groups/groups.yaml
236257

237258
## References and Resources
238259

@@ -256,5 +277,4 @@ guidelines:
256277
[Code of Conduct Committee]: /committee-code-of-conduct/README.md
257278
[Steering Committee]: https://git.k8s.io/steering
258279
[moderator request]: https://github.com/kubernetes/community/issues/new/choose
259-
[moderator template]: https://git.k8s.io/community/.github/ISSUE_TEMPLATE/moderator_application.md
260280
[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

Comments
 (0)