diff options
Diffstat (limited to 'communication')
| -rw-r--r-- | communication/moderation.md | 179 | ||||
| -rw-r--r-- | communication/moderators.md | 80 |
2 files changed, 156 insertions, 103 deletions
diff --git a/communication/moderation.md b/communication/moderation.md index accdd661..4ba5af7d 100644 --- a/communication/moderation.md +++ b/communication/moderation.md @@ -1,38 +1,58 @@ # Moderation on Kubernetes Communications Channels + This page describes the rules and best practices for people chosen to moderate Kubernetes communications channels. This includes Github, Slack, forums, mailing lists, YouTube, Zoom, and any property listed in the SIG Contributor Experience -[charter](/sig-contributor-experience/charter.md#code-binaries-and-services). +[charter]. -- Check the [centralized list of administrators] for contact information. +- Check the [centralized list of administrators][moderators] for contact + information. - Some Kubernetes properties, like the Twitter account, are managed by the CNCF. +--- + +- [Selection of Moderators](#selection-of-moderators) + - [Moderators Pro Tempore](#moderators-pro-tempore) +- [Rotation of Moderators](#rotation-of-moderators) +- [Roles and Responsibilities](#roles-and-responsibilities) +- [Escalation Procedures](#escalation-procedures) +- [Platform Specific Guidelines](#platform-specific-guidelines) + - [Discuss](#discuss) + - [Mailing list](#mailing-list) + - [Slack](#slack) + - [Youtube](#youtube) + - [Zoom](#zoom) +- [References and Resources](#references-and-resources) + +--- + ## Selection of Moderators -Each Kubernetes property has a certain set of [moderators](./moderators.md) who -are responsible for keeping it safe and a fun place to participate. +Each Kubernetes property has a certain set of [moderators] who +are responsible for keeping it safe and a fun place to participate. Moderators are selected by following the criteria: Moderators _MUST_: -- Be a [Kubernetes member](/community-membership.md). +- Be a [member of the Kubernetes Organization](/community-membership.md). - Have experience moderating something or some equivalent level of community - management. + management. - Make themselves available during their primary working hours for their given timezone. -- Communicate their availability to their peer moderators when appropriate when - traveling or becoming unavailable for a period of time +- Communicate their availability to their peer moderators when appropriate, such + as when travelling or becoming unavailable for an extended period of time. - Understand that volunteering for this role might mean an occasional personal - time commitment or offhour duty. + time commitment or off-hour duty. The process for applying for moderatorship is as follows: - Sponsored by 2 existing moderators **Note the following requirements for sponsors**: - - Sponsors MUST have close interactions with the prospective member - e.g. - participating in the appropriate property, coordinating on issues, etc. + - Sponsors MUST have close interactions with the prospective member - + example: participating in the appropriate property, coordinating on + issues, etc. - Sponsors MUST be from multiple member companies to demonstrate integration across community. - Sponsors MUST take time zone coverage into account, each property should @@ -41,7 +61,7 @@ The process for applying for moderatorship is as follows: - Sponsors MUST ensure that nominees are familiar with the software they are using to moderate. - **[Open an issue][moderator request] against the kubernetes/community repo** - - Ensure your sponsors are @mentioned on the issue + - Ensure your sponsors are @mentioned on the issue. - Complete every item on the checklist ([preview the current version of the template][moderator template]) - Make sure that the list of contributions included is representative of your @@ -52,41 +72,43 @@ The process for applying for moderatorship is as follows: ### Moderators Pro Tempore Each property will have a list of moderators who cannot commit to full time -moderatorship, but are available during special events or circumstances or for -adhoc duties. +moderatorship, but are available during special events or circumstances that +might call for additional ad-hoc duties. For example if all moderators are attending a conference, pro tempore moderators may be assigned to monitor a property. + ## Rotation of Moderators Content moderation can be personally tiring, so primary Moderators _SHOULD_ rotate on a regular basis. - Primary moderators should evaluate their position(s) as a team _yearly_. - - Determine whether the moderation situation on the property is working. - - Rotate teams accordingly + - Determine whether the moderation situation on the property is working. + - Rotate teams accordingly. - Consider rotating in less experienced person to give them an opportunity to - participate - - Take into account time zone considerations + participate. + - Take into account time zone considerations. - Due to less workload Moderators Pro Tempore should be a lightweight role - - Primary moderators could consider switching to this role for a given amount - of time to allow for a healthy rotation + - Primary moderators should consider switching to this role for a given amount + of time to allow for a healthy rotation. + ## Roles and Responsibilities -As part of volunteering to become a moderator you are now representative of the -Kubernetes community and it is your responsibility to remain aware of your +As part of volunteering to become a moderator you are now a representative of +the Kubernetes community, and it is your responsibility to remain aware of your contributions in this space. These responsibilities apply to all Kubernetes official channels. -Moderators _MUST_: +Moderators _MUST_: - Take action as specified by these Kubernetes Moderator Guidelines. - You are empowered to take _immediate action_ when there is a violation. You do not need to wait for review or approval if an egregious violation has - occurred. Make a judgement call based on our Code of Conduct and Values (see - below). + occurred. Make a judgement call based on our [Code of Conduct] and Values + (see below). - Removing a bad actor or content from the medium is required, do NOT let it sit there. - Abide by the documented tasks and actions required of moderators. @@ -102,17 +124,17 @@ Moderators _MUST_: - Keep up with software/platform changes on the property they are responsible for. This might include new UI changes, new features, or other software changes. Moderators are encouraged to meet regularly to train themselves how - to be proficient with the platform. + to be proficient with the platform. - Report violations of the Code of Conduct to <conduct@kubernetes.io>. -Moderators _SHOULD_: +Moderators _SHOULD_: - Exercise compassion and empathy when communicating and collaborating with other community members. - Understand the difference between a user abusing the resource or just having difficulty expressing comments and questions in English. -- Be an example and role model to others in the community. In many cases you are - the some of the first people new contributors will interact with. +- Be an example and role model to others in the community. In many cases, + moderators are some of the first people new contributors will interact with. - Remember to check and recognize if you need take a break when you become frustrated or find yourself in a heated debate. - Help your colleagues if you recognize them in one of the [stages of burnout]. @@ -123,87 +145,94 @@ Moderators _SHOULD_: The Kubernetes [Code of Conduct Committee] 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 +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. This decision comes from the Code of Conduct committee, not the moderators. +rare. This decision comes from the Code of Conduct committee, not the moderators. + ## Escalation Procedures -In the event of large attacks the moderator and moderator team must enact the -following procedures: +In the event of large attacks the moderator team must enact the following +procedures: - The person on call should immediately concentrate on removing the offending content and asking for other on call moderators for help. That is their sole - responsibility. + responsibility. - The secondary person on call should immediately begin to take notes to document the incident, this will form the basis of a post-mortem. The 2nd - person on site is responsible for finding help and documenting the incident. -- The secondary person on call will escalate if necessary, if it's a one off - incident and the content is removed then the collective moderators can work on + person on site is responsible for finding help, and documenting the incident. +- The secondary person on call will escalate if necessary. If it's a one off + incident and the content is removed, then the collective moderators can work on a post-mortem and report the incident to primary moderators within 24 hours. - - If it's a sustained incident that needs more help the secondary will contact - a primary moderators as soon as possible. - - If appropriate, the next level of people to contact are the OWNERS of this - subproject - - If appropriate, the next level of people to contact are the [Code of Conduct - Committee] - - If appropriate, the next level of people to contact are the [Steering - Committee] + - If it's a sustained incident that needs more help, the secondary will contact + other primary moderators as soon as possible. + - If appropriate, the next level of people to contact are the OWNERS of the + subproject. + - If appropriate, the next level of people to contact is the [Code of Conduct + Committee]. + - If appropriate, the next level of people to contact is the [Steering + Committee]. - Moderators will have access to a private document with contact information of the appropriate people. -## Specific Guidelines + +## Platform Specific Guidelines These guidelines are for tool-specific policies that don't fit under a general umbrella. -### Discuss guidelines +### Discuss -- [Discuss guidelines](./discuss-guidelines.md) +- [Discuss Guidelines](./discuss-guidelines.md) +- [Moderators](./moderators.md#discuss.kubernetes.io) +- [Regional Moderators](./moderators.md#regional-category-moderators) -### Mailing list guidelines +### Mailing List -- [Mailing List guidelines](./mailing-list-guidelines.md) +- [Mailing List Guidelines](./mailing-list-guidelines.md) +- [Moderators](./moderators.md#mailing-list) ### Slack -- [Slack guidelines](./slack-guidelines.md) +- [Slack Guidelines](./slack-guidelines.md) +- [Moderators](./moderators.md#slack) ### YouTube -- Moderators should check the Comments section in the community tab regularly for -published comments and the "holds for review" sections to see if comments are being flagged by the system. -- We do NOT use YouTube comments during our live streams, these are checked as OFF in the settings. +- Moderators should check the Comments section in the community tab regularly + for published comments and the "hold for review" sections to see if comments + are being flagged by the system. +- We do NOT use YouTube comments during our live streams, these are checked as + OFF in the settings. +- [Youtube Guidelines](./K8sYoutubeCollaboration.md) +- [Moderators](./moderators.md#youtube-channel) + +### Zoom -### Zoom +- [Zoom Guidelines](./zoom-guidelines.md) +- [Moderators](./moderators.md#zoom) -- [Zoom guidelines](./zoom-guidelines.md) -### References and Resources +## References and Resources Thanks to the following projects for making their moderation guidelines public, allowing us to build on the shoulders of giants. Moderators are encouraged to learn how other projects moderate and learn from them in order to improve our guidelines: -- Mozilla's [Forum Moderation - Guidelines](https://support.mozilla.org/en-US/kb/moderation-guidelines) -- OASIS [How to Moderate a Mailing - List](https://www.oasis-open.org/khelp/kmlm/user_help/html/mailing_list_moderation.html) -- Community Spark's [How to effectively moderate - forums](http://www.communityspark.com/how-to-effectively-moderate-forums/) -- [5 tips for more effective community - moderation](https://www.socialmediatoday.com/social-business/5-tips-more-effective-community-moderation) -- [8 Helpful Moderation Tips for Community - Managers](https://sproutsocial.com/insights/tips-community-managers/) -- [Setting Up Community Guidelines for - Moderation](https://www.getopensocial.com/blog/community-management/setting-community-guidelines-moderation) - -[centralized list of administrators]: ./moderators.md#mailing-lists -[Code of Conduct]: /code-of-conduct.md -[Kubernetes Community Values]: /values.md +- Mozilla's [Forum Moderation Guidelines](https://support.mozilla.org/en-US/kb/moderation-guidelines) +- OASIS [How to Moderate a Mailing List](https://www.oasis-open.org/khelp/kmlm/user_help/html/mailing_list_moderation.html) +- Community Spark's [How to effectively moderate forums](http://www.communityspark.com/how-to-effectively-moderate-forums/) +- [5 tips for more effective community moderation](https://www.socialmediatoday.com/social-business/5-tips-more-effective-community-moderation) +- [8 Helpful Moderation Tips for Community Managers](https://sproutsocial.com/insights/tips-community-managers/) +- [Setting Up Community Guidelines for Moderation](https://www.getopensocial.com/blog/community-management/setting-community-guidelines-moderation) + +[charter]: /sig-contributor-experience/charter.md#code-binaries-and-services +[moderators]: ./moderators.md +[Code of Conduct]: /code-of-conduct.md +[Kubernetes Community Values]: /values.md [stages of burnout]: https://opensource.com/business/15/12/avoid-burnout-live-happy -[Code of Conduct Committee]: /committee-code-of-conduct -[Steering Committee]: /committee-steering +[Code of Conduct Committee]: /committee-code-of-conduct/README.md +[Steering Committee]: https://git.k8s.io/steering [moderator request]: https://github.com/kubernetes/community/issues/new/choose [moderator template]: https://git.k8s.io/community/.github/ISSUE_TEMPLATE/moderator_application.md diff --git a/communication/moderators.md b/communication/moderators.md index 340d9333..51560325 100644 --- a/communication/moderators.md +++ b/communication/moderators.md @@ -1,19 +1,24 @@ # Community Moderators -The following people are responsible for moderating/administrating Kubernetes communication channels and their home time zone. -See our [moderation guidelines](./moderation.md) for policies and recommendations. +The following people are responsible for moderating/administrating Kubernetes +communication channels and their home time zone. See our +[moderation guidelines] for policies and recommendations. ## Mailing Lists ### kubernetes-dev -#### Administrators (3) +#### Administrators + +Administrator seats: 3 - Paris Pittman - PT -- Aaron Crickenberger - PT +- Aaron Crickenberger - PT - Open -#### Primary Moderators (7) +#### Primary Moderators + +Primary moderators seats: 7 - Jorge Castro (@castrojo) - ET - Jaice Singer DuMars - (@jdumars) - PT @@ -23,7 +28,9 @@ See our [moderation guidelines](./moderation.md) for policies and recommendation - Open - Open -#### Moderators Pro Tempore (5) +#### Moderators Pro Tempore + +Moderators pro tempore seats: 5 - Open - Open @@ -34,48 +41,51 @@ See our [moderation guidelines](./moderation.md) for policies and recommendation ## GitHub Note that this team is not only responsible for the project's Github -administration, but also moderation of issues, PRs, etc. +administration, but also moderation of issues, PRs, etc. -- [GitHub Administration - Team](https://github.com/kubernetes/community/tree/master/github-management#github-administration-team) +- [GitHub Administration Team] -## discuss.kubernetes.io +## Discuss ### Administrators +Administrators seats: 4 + - Paris Pittman (@parispittman) - PT -- Jorge Castro (@castrojo) - ET +- Jorge Castro (@castrojo) - ET - Bob Killen (@mrbobbytables) - ET - Jeffrey Sica (@jeefy) - ET Note, due to how the software is designed, dedicated moderators are not required -for discuss, the [trust -system](https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/) -in place allows for self moderation. In this case administrators act as -exception handlers. Regional moderators are required for language/cultural -reasons, (ie. we can't expect a community member who doesn't speak a language to -be able to effectively moderate). +for discuss, the [trust system] in place allows for self moderation. In this +case administrators act as exception handlers. Regional moderators are required +for language/cultural reasons, (ie. we can't expect a community member who +doesn't speak a language to be able to effectively moderate). + +### Regional Category Moderators -### Regional category moderators +Regional category moderators seats (per category): 3 -- [Chinese] (3) +- [Chinese] - Peter (Xiang Peng) Zhao (@xiangpengzhao) - CST - Yang Li (@idealhack) - CST - Puja Abbassi (@puja108) - CET -- [German] (3) +- [German] - Puja Abbassi (@puja108) - CET - Michael Hausenblas (@mhausenblas) - WET - Daniel Holbach (@dholbach) - CET -- [Italian] (3) +- [Italian] - Jacopo Nardiello (@jnardiello) - CET - Open - Open -- [Ukrainian] (3) +- [Ukrainian] - Ihor Dvoretskyi (@idvoretskyi) - EET - Open - Open -## YouTube Channel (9) +## YouTube Channel + +Youtube owners seats: 2 ### Owners @@ -84,6 +94,8 @@ be able to effectively moderate). ### Primary Moderators +Moderators seats: 10 + - Ihor Dvoretskyi (@idvoretskyi) - EET - Jeffrey Sica (@jeefy) - ET - Jorge Castro (@castrojo) - ET @@ -93,7 +105,9 @@ be able to effectively moderate). - Open - Open -### Moderators Pro Tempore (3) +### Moderators Pro Tempore + +Moderators pro tempore seats: 3 These are listed as "Communications Managers" in YouTube @@ -103,11 +117,15 @@ These are listed as "Communications Managers" in YouTube ## Slack -#### Owner (1) +#### Owner + +Owners seats: 1 - Chris Aniszczyk (@caniszczyk) - CT (non-admin role) -#### Moderators (9) +#### Moderators + +Moderators seats: 9 - Bob Killen (@mrbobbytables) - ET - Ihor Dvoretskyi (@idvoretskyi) - EET @@ -119,7 +137,9 @@ These are listed as "Communications Managers" in YouTube - Jorge Alarcon (@alejandrox1) - ET - Yang Li (@idealhack) - CST -#### Moderators Pro Tempore (9) +#### Moderators Pro Tempore + +Moderators pro tempore seats: 9 - Dylan Graham (@DylanGraham) - AEST - Open @@ -133,13 +153,17 @@ These are listed as "Communications Managers" in YouTube ## Zoom +Administrators seats: 4 + - Paris Pittman (@parispittman) - PT - Jorge Castro (@castrojo) - ET - Open - Open - License and main account controlled by the CNCF - +[moderation guidelines]: ./moderation.md +[GitHub Administration Team]: https://git.k8s.io/community/github-management#github-administration-team +[trust system]: https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/ [Chinese]: https://discuss.kubernetes.io/t/about-the-chinese-category/2881 [German]: https://discuss.kubernetes.io/t/about-the-german-category/3152 [Italian]: https://discuss.kubernetes.io/t/about-the-italian-category/2917/2 |