diff options
| author | Avinesh Tripathi <73980067+AvineshTripathi@users.noreply.github.com> | 2022-11-23 13:17:37 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-23 13:17:37 +0530 |
| commit | de5fa62cbd1db672014851f05b2634e16b8cff58 (patch) | |
| tree | c3df758d461e4566d698cca462bcd439a9f16372 /communication | |
| parent | 38c1e81aa4d5404ab3389ef54c77642ca84c1166 (diff) | |
| parent | 62b16d1aafdd744708c2f5243f90e858806bff95 (diff) | |
Merge branch 'kubernetes:master' into patch-3
Diffstat (limited to 'communication')
37 files changed, 452 insertions, 286 deletions
diff --git a/communication/OWNERS b/communication/OWNERS index 01c24fe2..78e2cbc6 100644 --- a/communication/OWNERS +++ b/communication/OWNERS @@ -1,7 +1,6 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: - - parispittman - jdumars - idvoretskyi - jeefy @@ -9,10 +8,10 @@ reviewers: - markyjackson-taulia approvers: - mrbobbytables - - parispittman - sig-contributor-experience-leads emeritus_approvers: - castrojo + - parispittman labels: - sig/contributor-experience - area/community-management diff --git a/communication/README.md b/communication/README.md index f78eae1b..54033338 100644 --- a/communication/README.md +++ b/communication/README.md @@ -1,7 +1,7 @@ # Communication The Kubernetes community abides by the [Kubernetes code of conduct] on all of -communication platforms that we moderate listed below with noted exceptions. +the communication platforms that we moderate listed below with noted exceptions. Here is an excerpt from the code of conduct: > _As contributors and maintainers of this project, and in the interest @@ -27,11 +27,11 @@ agenda/notes, and can be found on their READMEs and on the community groups/[SIGs] page. You can actively or passively participate in one of the following ways: -- The community groups public meeting(s) listed in the above community groups page +- The community group's public meeting(s) listed on the above community groups page - Every Third Thursday at our [monthly community meeting] over [zoom] at [10am US Pacific Time] - Intro sessions at KubeCon/CloudNativeCon live or [recordings on YouTube] -Nevertheless, below find a list of many general channels, groups and meetings +Nevertheless, below find a list of many general channels, groups, and meetings devoted to the Kubernetes project. Please check the guidelines and any relevant chat/conversation history before posting. Spam and sales pitches are not tolerated on these platforms. @@ -98,7 +98,7 @@ and security issues - [Discuss Kubernetes] is a forum where Kubernetes users trade notes with sections for contributors and all kinds of ecosystem related content - Additional Google groups exist and can be joined for discussion related to each -community groups as noted above. These are linked from the [SIG list][SIGs]. +community group as noted above. These are linked from the [SIG list][SIGs]. ### Calendar & Meetings @@ -154,14 +154,14 @@ resources. - [kubeweekly] - owned by cncf and curated by community members listed on the site. Collection of news, blogs, talks, and events for all things Kubernetes. send submissions to kubeweekly@cncf.io -- [LWKD] - weekly newsletter that summarizes changes to Kubernetes code, development, +- [LWKD] - a weekly newsletter that summarizes changes to Kubernetes code, development, and release schedules. Written by two members of SIG-Contribex. ### Conferences, Meetups, Summits, and Face to Face Meetings CNCF is the main driver for all KubeCon + CloudNativeCons, Kubernetes Forums, and the [Kubernetes Meetup Pro] program on meetup.com. KubeCon + CloudNativeCon, -held every spring in Europe, summer in China, and winter in North America. +is held every spring in Europe, summer in China, and winter in North America. Information about these and other community events is available on the CNCF [events] pages. diff --git a/communication/marketing-team/CHARTER.md b/communication/contributor-comms/CHARTER.md index 68f3ba13..ee988acc 100644 --- a/communication/marketing-team/CHARTER.md +++ b/communication/contributor-comms/CHARTER.md @@ -36,4 +36,4 @@ Things change, priorities get optimized, life happens. Having an easy on and off In the case where no shadow is available, other Marketing Council team members have the responsibility to cover the role. Concerns for time or ability to cover work can be escalated to advisors and SIG Contributor Experience leads as necessary. -[Marketing Council](/communication/marketing-team/role-handbooks/council.md) +[Marketing Council](/communication/contributor-comms/role-handbooks/council.md) diff --git a/communication/marketing-team/OWNERS b/communication/contributor-comms/OWNERS index e20309c7..1145ed7f 100644 --- a/communication/marketing-team/OWNERS +++ b/communication/contributor-comms/OWNERS @@ -3,14 +3,13 @@ reviewers: - chris-short - onlydole - - parispittman approvers: - - parispittman - Pensu - rajula96reddy - kaslin emeritus_approvers: - mbbroberg + - parispittman labels: - sig/contributor-experience - area/contributor-comms diff --git a/communication/marketing-team/README.md b/communication/contributor-comms/README.md index c7a2b0a0..76cd9493 100644 --- a/communication/marketing-team/README.md +++ b/communication/contributor-comms/README.md @@ -1,7 +1,6 @@ -# Upstream Marketing +# Contributor Communications -The Upstream Marketing Contributor Communications team (Contributor Comms for short) is part of the `community-management` subproject in -[Contributor Experience]. View our [charter] to learn more about us. +The Contributor Communications team (Contributor Comms for short) is part of the `community-management` subproject in [Contributor Experience]. View our [charter] to learn more about us. ## Purpose @@ -9,11 +8,13 @@ To better inform the Kubernetes contributor community and highlight their work t | Area & Handbook Link | Team | Notes | | --- | --- | --- | -| [Marketing Council] Program Lead | @mbbroberg, shadow: @JasonMorgan,| advisors: @parispittman, @chris-short | -| [Marketing Council] Promotion Lead |@kaslin, shadow: @Debanitrkl | advisors: @parispittman, @chris-short | -| [Marketing Council] Liaison Lead | @rajula96reddy, shadow: `OPEN` | Shadow role is available. | -| Liaisons | release: @rajula96reddy, docs: `OPEN` | Are you a SIG that wants support from Contributor Comms? Ping the liaison lead! | -| [Storytellers] & other members | @kunal-kushwaha, @gkarthiks, @dewan-ahmed, @joelbyronbarker, Sladyn Nunes, @hpopal11 | New to Contributor Comms? Add your name here! +| Subproject Lead | @kaslin, @chris-short | Shadow role is available. | +| [Social Media Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Social-Media.md) |@kaslin | Shadow role is available. | +| [Comms Tech Lead](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md) | @imnmo | Shadow role is available. | +| [Comms Event Lead] | @AvineshTripathi | Shadow role is available. | +| [Comms Blog Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/blog-coordinator.md) | @fsmunoz | Shadow role is available. | +| [Storytellers] & other members | @hpopal11, @Atharva-Shinde | New to Contributor Comms? Add your name here! | +| Emeritus | @parispittman, @mbbroberg | ## Contact Us! @@ -38,9 +39,11 @@ Let us know you are interested and if you have any questions. [charter]: ./CHARTER.md [Could be you!]: #could-be-you [Contributor Experience]: /sig-contributor-experience -[Marketing Council]: ./role-handbooks/editor.md [Internal Communications]: ./role-handbooks/internal-marketing.md [Social Media]: ./role-handbooks/social-media.md +[Comms Tech Lead]: ./role-handbooks/Comms-Tech-Lead.md +[Comms Event Lead]: ./role-handbooks/Comms-Event-Lead.md +[Comms Blog Coordinator]: ./role-handbooks/blog-coordinator.md [Storytellers]: ./role-handbooks/storytellers.md [Designer]: ./role-handbooks/wip-roles.md [kubernetes/community]: https://github.com/kubernetes/community/issues diff --git a/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md b/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md new file mode 100644 index 00000000..3a5605de --- /dev/null +++ b/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md @@ -0,0 +1,55 @@ +# Comms Tech Lead Role Handbook + +## Overview + +This handbook outlines expectations and responsibilities for Tech Leads as well as Contributor Comms team members who wish to contribute to technical efforts. + +Tech leads' contributions further the Contributor Comms team's efforts to communicate contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets), and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message). + +[contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location. + +Along with contributor-site there exist two automation tools that help: +1. To create tweets (k8scontributors) via GitHub actions (see: [workflow](https://github.com/kubernetes-sigs/contributor-tweets/blob/main/.github/workflows/main.yml)) +2. To broadcasts messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message)) + +The [contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) utilizes open source Github action [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweet approval from an issue. + +## Minimum Skills and Requirements + +- Are a member of the [Kubernetes GitHub Org] +- Good knowledge of Node.js, Hugo(docsy theme and frontmatter) +- Have a basic experience in Go (for Slack bot) +- Have a good understanding of Github actions +- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack + +### Expected Time Investment + +Team leads: 4-5 hours per week. +Team members: 2-3 hours per week. + +## General Expectations + +- Be welcoming, be yourself +- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site, tweets, and, slack bot +- Have an understanding of what an issue is about and able to triage them, or know who to contact to determine the required information +- Coordinate work to fix any issues in automation tools to ensure valid tweet requests are fulfilled +- Train new leads + +Team members will be expected to keep an eye out for news or issues related to slack bot or Github automation. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack. + +## Associates Overview (Shadow) + +Team members who wish to become technical leads shadow should express this desire to the current lead. + +Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including: + +* General familiarity with our repositories and automation tools +* Willingness and ability to follow up with contributors about issues, on Github, Slack, and email, as appropriate +* Ability to file well-crafted Kubernetes issues, including labeling and prow commands +* General knowledge of our SIG system and SIGs' areas of responsibility or knowing who to contact to determine the required information + +Additionally, the following qualifications make a candidate more suitable for the technical team, but are not requirements: + +* Prior involvement with the Contributor Comms team and the contributor experience team +* Experience with Github actions and Github workflow +* A basic understanding of Golang diff --git a/communication/marketing-team/role-handbooks/Social-Media.md b/communication/contributor-comms/role-handbooks/Social-Media.md index 305082dc..f1a1b36b 100644 --- a/communication/marketing-team/role-handbooks/Social-Media.md +++ b/communication/contributor-comms/role-handbooks/Social-Media.md @@ -24,9 +24,9 @@ Team members: 1-3 hour per week. ## General Expectations -- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Rules for social posts and more can be found in [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md) - Be welcoming, be yourself -- Understanding, communicating, and setting/adjusting [social guidelines](https://github.com/kubernetes/community/blob/master/communication/marketing-team/storytelling-resources/social-guidelines.md) +- Understanding, communicating, and setting/adjusting [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md) - Coordinating work to create tweets, ensuring tweet requests are fulfilled - Working with other Contributor Comms leads, such as the Event Coordinator Lead, on social media tasks - Approving tweet PRs on [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) diff --git a/communication/contributor-comms/role-handbooks/blog-coordinator.md b/communication/contributor-comms/role-handbooks/blog-coordinator.md new file mode 100644 index 00000000..9eef7b37 --- /dev/null +++ b/communication/contributor-comms/role-handbooks/blog-coordinator.md @@ -0,0 +1,48 @@ +# Blog Coordinator Handbook + +This handbook outlines expectations and responsibilities for Blog coordinator as well as Contributor Comms team members who wish to contribute to blogging activities. + +Writing and sharing articles is one of the ways through which Kubernetes contributors add to the community, and the Blog Coordinator role exists to + +1. Serve as an initial point of contact for content suggestions +2. Help contributors to navigate the existing publishing processes +3. Assist in determining the final publishing targets of the content. +4. Coordinate with SIG-Docs in the publishing process, namely by following and improving the Blogging Guidelines. +5. Coordinate with the rest of the Contributor Comms team, and specifically the Social Media Coordinator, in the best ways to broaden external awareness of published content. + +The [Kubernetes Contributor Blog](https://www.kubernetes.dev/blog/) is one of the most direct points of entry for those that want to share with a wider audience. The role of the Blog Coordinator is to guide those that want to contribute in the best way to do so, while coordinating with the rest of the team (including other Contributor Comms team members) to assign editors, reviewers and other roles to new submissions. + +The Blog Coordinator has an active involvement in defining, with others, the [Blogging Guidelines](https://hackmd.io/@fsm/blog-guidelines), and should constantly seek to improve them, with an eye on the improvement of the contributor experience. + + +### Minimum Skills and Requirements + +Those in this role should ideally: + +* Be a member of the [Kubernetes GitHub Org](https://github.com/kubernetes/) +* Have some familiarity with blogging platforms and editing tools; specific knowledge of Markdown, GitHub and Hugo is a plus. +* Be available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack + +#### Expected time commitment + +* Team leads: 3-5h per week. +* Team members: 1-3h per week. + +### General Expectations + +1. Be ready to help those wanting to contribute to the blogs. +2. Understand the Blogging Guidelines and assist contributors in following them. +3. Help in determining applicability of the proposed content, with the rest of the team: this includes discussion in the Slack channel or regular meeting. +4. Identify team members that can review blog submissions. +5. Discuss with SIG-Docs, when needed, for possible publication in the main Kubernetes site. +6. Review blog submissions. +7. Open the blog submission PR (with the author as Co-author), or find someone that can assist in this tasks within the Contributor Comms team. +8. Follow up submitted PRs and help with the approval process. + +### Associates Overview (Shadow) + +Team members who which to become Blogging Leads should express their desire to the current lead; leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan to take on responsibility, including: + +* Become a reviewer of new submitted content. +* Open the PRs and follow them through. +* Provide assistance to new contributors that are asking how to submit content. diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/contributor-comms/role-handbooks/storytellers.md index 454f26c9..c65a0a01 100644 --- a/communication/marketing-team/role-handbooks/storytellers.md +++ b/communication/contributor-comms/role-handbooks/storytellers.md @@ -2,19 +2,19 @@ ## Overview -Upstream Marketing depends on great storytelling to get the message out about our amazing community. +Contributor Comms depends on great storytelling to get the message out about our amazing community. -It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok–it's not always there for entertainment purposes. It is about providing valuable information and get you were you need to go. But that said, an important message can be lost without an entertaining messenger. +It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok–it's not always there for entertainment purposes. It is about providing valuable information and getting you where you need to go. But that said, an important message can be lost without an entertaining messenger. In this role, Storytellers are here to help Kubernetes contributors hear the latest news in the most entertianing ways. Storytellers will take us on journeys through words and visuals to help us craft. ## Workflow ⚡️ -Storytelling is welcome in any medium that can be supported by the Upstream Marketing team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines]. +Storytelling is welcome in any medium that can be supported by the Contributor Comms team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines]. Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder]. -### Upstream Marketing Process +### Contributor Comms Process #### Idea Paths @@ -22,7 +22,7 @@ There are multiple ways to successfully contribute a Kubernetes blog post. Here **To start:** -* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Upstream Marketing team](https://github.com/kubernetes/community/tree/master/communication/marketing-team) meeting to discuss it ahead of time +* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Contributor Comms team](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) meeting to discuss it ahead of time **To write:** @@ -30,17 +30,17 @@ There are multiple ways to successfully contribute a Kubernetes blog post. Here * A draft can be written in: * Google Docs or * Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/)) -* Connect with a storyteller -- if you reach out to Upstream Marketing, you will be paired with someone to help you through writing, editing, and getting your article published +* Connect with a storyteller -- if you reach out to Contributor Comms, you will be paired with someone to help you through writing, editing, and getting your article published * Discussion happens via GitHub issue or through working group meetings -* This includes working with Upstream Marketing team to polish, and format your blog post - * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/marketing-team/blog-guidelines.md#how-to-write-an-effective-blog) +* This includes working with Contributor Comms team to polish, and format your blog post + * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blog-guidelines.md#how-to-write-an-effective-blog) * There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post) When it's ready, submit the blog post: * Go to the `kubernetes/website` repository * Open a PR with your added blog post - * If you need help with this process, Upstream Marketing will look to pair you with someone for PR and shepherd it through the review cycle + * If you need help with this process, Contributor Comms will look to pair you with someone for PR and shepherd it through the review cycle Or if you already have everything you think you need you can: @@ -72,7 +72,7 @@ Anyone is welcome to contribute when they have time. The core expectation of sto If you would like to be listed as a member of the team, here are the expectations: 1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue. -2. Storytellers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active. +2. Storytellers are expected to attend at least one Contributor Comms meeting a month or check-in to remain active. 3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it. 4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project. diff --git a/communication/contributor-comms/storytelling-resources/blog-guidelines.md b/communication/contributor-comms/storytelling-resources/blog-guidelines.md new file mode 100644 index 00000000..cadf0cdd --- /dev/null +++ b/communication/contributor-comms/storytelling-resources/blog-guidelines.md @@ -0,0 +1,92 @@ +# Contributor Comms Blog Guidelines + +This initiative falls under the [Contributor Comms Charter](./CHARTER.md). + +We are looking for Kubernetes-curious community members who are **interested in writing** and **care about getting the word out** to our huge community of users, developers, and contributors of all types. Here's how to get involved. + +## Requested Content + +We are looking for content related to the contributor experience and with increasing the visibility of Kubernetes and how it is developed: this includes interviews with SIGs, articles on how to better use existing tools and processes, and in general tips and suggestions on how to collaborate. + +Other types of content, like Kubernetes capabilities, tutorials, and technical articles, are better suited for the [SIG-Docs blogging initiative](/sig-docs/blog-subproject/README.md). + +## Where to publish + +As mentioned, the focus of the Contributor Experience articles is targeted at those that contribute to Kubernetes, but sometimes it's not obvious were a specific theme will fit. The following are the most common situations: + +1. Article is just for [k8s.dev](http://k8s.dev/blog): this is when it is relevant for the contributor community, and not necessarily for Kubernetes end-users. An example is an article explaining how to use some specific tool or automation that helps with the Kubernetes development process. +2. Article is just for [kubernetes.io](https://kubernetes.io/blog/): when the article targets Kubernetes end-users, and not specifically the contributor community. Examples include most technical articles on Kubernetes features, updates on new features and deprecations, etc. +3. Article is relevant for both: sometimes, an article will be relevant to both the Kubernetes end-users, and the contributor community. Examples include interviews with SIGs and WGs, articles on technical aspects that are important for the contributor community, etc. + +The decision on what is the right option will be made jointly by the SIG Contribex Comms and the SIG Docs Blogging editorial team: as a content writer you shouldn't be overly concerned about it, expect in how it can change the approval process, as described below. + +## Submission and review process + +The quickest way to get involved is to let the team in [#sig-contribex-comms](https://kubernetes.slack.com/archives/C03KT3SUJ20) know that you have an idea for an article; the team will identify the best target for your submission and liaison with the necessary teams, if needed. To reduce the amount of editing done directly in GitHub, a two-stage approach is highly recommended. + +This process is initiated in [#sig-contribex-comms](https://kubernetes.slack.com/archives/C03KT3SUJ20) and uses the processes from the SIG Docs blog [subproject](/sig-docs/blog-subproject/README.md), and is broadly as follows: + +1. Present your idea to the community, by going to the [#sig-contribex-comms](https://kubernetes.slack.com/archives/C03KT3SUJ20) Slack channel, or by joining the [weekly meeting](https://docs.google.com/document/d/1KDoqbw2A6W7rLSbIRuOlqH8gkoOnp2IHHuV9KyJDD2c). This will make it easier to coordinate effort and avoid duplicate effort, as well as to gather initial suggestions around the article scope. +2. The submission idea will be reviewed by the team, including the decision on where to publish it; someone from the SIG Contribex Comms team will reach out to the [#sig-docs-blog](https://kubernetes.slack.com/archives/CJDHVD54J) editorial team to clarify if the content is adequate for republishing in the main Kubernentes blog. At this stage an editor should be assigned to follow-up the process with you. +3. Create your proposal draft in [Google Docs](https://docs.google.com/) or HackMD (https://hackmd.io), and ask for a review in [the channel](https://kubernetes.slack.com/archives/C03KT3SUJ20). This will facilitate easier editing, especially if major changes or restructuring is needed. Take into account the [documentation style guide](https://kubernetes.io/docs/contribute/style/style-guide/): these guidelines can help in improving the readability of your article, especially in terms of the use of Kubernetes terminology. +4. Once you have reflected any feedback in the proposal draft, announce that the article is ready for submission (again, in the channel or in one of the weekly meetings): the assigned editor will use the final text to open the PR, adding you as a Co-author +5. (Optional) If the submission will be mirrored in the main Kubernetes site, a second PR will be oped by the editor, but on the main repository, and after being approved in the `contributor-site` one. + +For now, our official process is to use [SIG Docs' system](/sig-docs/blog-subproject/README.md), with one change: instead of directly creating the file in the Kubernetes site repository, as instructed abovem it's initially created in the [contributor-site](https://github.com/kubernetes/contributor-site), in the appropriate folder (i.e. the right year in `contributor-site/content/en/blog/`). + +This will lead to an initial review process before it gets mirrored to the main Kubernetes site. + +### Editor instructions + +Once the text is final, an editor will open the PR. This facilitates the approval process and prevents articles with massive restructuring or changes needed to be submitted to GitHub, something that makes the review process substantially more difficult. + +In order to keep the authorship information (which will make the submission count towards the contribution of the article author), editors must [add the original author as a co-author](https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors). This is done by adding `Co-authored-by: original-author-name <original-author@example.com>` to the commit message. + +The number of PRs depends on where the article will be published: + +1. If it's solely for the Contributor site: the PR should be opened in the [contributor-site](https://github.com/kubernetes/contributor-site), after which the process ends. +2. If it's to be mirrored in the main Kubernetes blog: after the previous step, a new PR is opened on [kubernetes/website](https://github.com/kubernetes/website), mentioning the original PR. The SIG-Docs Blog editorial team will, in this case, already been notified and involved in the initial PR. + + +## Blogger Expectations, Responsibilities, and Info + +Anyone is welcome to contribute when they have time. + +If you would like to be listed as a member of the team, here are the expectations: + +1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue. +2. Bloggers are expected to attend at least one Contributor Comms team meeting a month or check-in to remain active. +3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it. +4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project. + +## How to Write an Effective Blog + +Keep the following points in mind as you write in order to speed up the review process: + +* Use inclusive language understandable by everyone + * Rephrase gendered pronouns (change "he" or "she" to "they" or adjust to remove) + * Remember nothing is simple when you're starting out (remove "just," "simply", and "easy") + * Define terminology or acronyms (do not assume people know what a term means) + * Shy away from jargon and colloquial expressions + * Write clearly and avoid ambiguous sentences +* Emphasize the things you want readers to remember; tell a story + * Stay on topic and stick to the facts + * Design a beginning, middle, and end to your story with a clear call to action + * Provide evidence and data where applicable, to back up your message +* Make the article visually appealing + * Include at least one image (and use public domain or Creative Commons licensed ones) + * Prefer inclusive images like those from [WOCinTech](https://www.flickr.com/photos/wocintechchat/) and [Queer in Tech](https://www.flickr.com/photos/mapbox/albums/72157713100349311) + * Find images on sites like [Creative Commons](https://search.creativecommons.org/), [Pexels](https://www.pexels.com/public-domain-images/), and [Unsplash](https://unsplash.com/images/stock/public-domain)) +* Be accountable and honest as an author + * Remove anything that lacks adequate evidence + * Avoid interjecting personal reactions + * Ensure that the blog post is reviewed by the anyone being mentioned in the piece + * As the author, never talk about your employer, sell, promote, or pitch; this is about upstream community endeavours and the individuals and groups that create it +* Follow the [documentation style guide](https://kubernetes.io/docs/contribute/style/style-guide/). + +## Further Recommendations + +The following are helpful resources for authoring articles: + +* [Creating Quality Content (For Search Engines and People)](https://moz.com/blog/quality-blog-content) +* [How to write effective documentation for your open source project](https://opensource.com/article/20/3/documentation) diff --git a/communication/marketing-team/storytelling-resources/event-checklist.md b/communication/contributor-comms/storytelling-resources/event-checklist.md index 48549da4..48549da4 100644 --- a/communication/marketing-team/storytelling-resources/event-checklist.md +++ b/communication/contributor-comms/storytelling-resources/event-checklist.md diff --git a/communication/marketing-team/storytelling-resources/example-interview-qs-sig-windows.md b/communication/contributor-comms/storytelling-resources/example-interview-qs-sig-windows.md index 51fe382c..51fe382c 100644 --- a/communication/marketing-team/storytelling-resources/example-interview-qs-sig-windows.md +++ b/communication/contributor-comms/storytelling-resources/example-interview-qs-sig-windows.md diff --git a/communication/marketing-team/storytelling-resources/example-topics.md b/communication/contributor-comms/storytelling-resources/example-topics.md index e71c29d3..e71c29d3 100644 --- a/communication/marketing-team/storytelling-resources/example-topics.md +++ b/communication/contributor-comms/storytelling-resources/example-topics.md diff --git a/communication/marketing-team/storytelling-resources/multichannel-communications.md b/communication/contributor-comms/storytelling-resources/multichannel-communications.md index dd0b786f..dd0b786f 100644 --- a/communication/marketing-team/storytelling-resources/multichannel-communications.md +++ b/communication/contributor-comms/storytelling-resources/multichannel-communications.md diff --git a/communication/marketing-team/storytelling-resources/sig-spotlight-blog-process.md b/communication/contributor-comms/storytelling-resources/sig-spotlight-blog-process.md index 056047d5..056047d5 100644 --- a/communication/marketing-team/storytelling-resources/sig-spotlight-blog-process.md +++ b/communication/contributor-comms/storytelling-resources/sig-spotlight-blog-process.md diff --git a/communication/marketing-team/storytelling-resources/social-guidelines.md b/communication/contributor-comms/storytelling-resources/social-guidelines.md index 6871ceb6..ecb5b221 100644 --- a/communication/marketing-team/storytelling-resources/social-guidelines.md +++ b/communication/contributor-comms/storytelling-resources/social-guidelines.md @@ -4,7 +4,7 @@ ## General guidelines -All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](./CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. +All messaging must be consistent with the values and principles of the project and the [ethos/vision of the team](/communication/contributor-comms/CHARTER.md#ethosvision). Messaging should be positive and uplifting. Be aware that sarcasm and/or jokes are generally hard to read over a medium such as social media. Original messages should come out of this teams' accounts at least twice a week (if not more). However, there should be no more than three tweets per hour (including retweets). Retweets, likes, and responses are unlimited, but they should be used thoughtfully to encourage inclusive and kind participation. Use scheduling software as needed to space out messages. All messages should serve a purpose: have an action and/or thumbnail image ("click link for details," "register today," etc. are example actions). Never include photos, user handles, or other personally identifiable information without explicit permission. diff --git a/communication/marketing-team/team-resources.md b/communication/contributor-comms/team-resources.md index 96e27997..96e27997 100644 --- a/communication/marketing-team/team-resources.md +++ b/communication/contributor-comms/team-resources.md diff --git a/communication/discuss-guidelines.md b/communication/discuss-guidelines.md index dded2ff6..11b5d992 100644 --- a/communication/discuss-guidelines.md +++ b/communication/discuss-guidelines.md @@ -47,7 +47,7 @@ throughout the project, and includes all communication mediums. ## Privacy Policy -Discuss adheres to the the [Linux Foundation Privacy Policy]. +Discuss adheres to the [Linux Foundation Privacy Policy]. ## Admins diff --git a/communication/mailing-list-guidelines.md b/communication/mailing-list-guidelines.md index 50c3713a..f6a94500 100644 --- a/communication/mailing-list-guidelines.md +++ b/communication/mailing-list-guidelines.md @@ -136,7 +136,7 @@ list, and again for the members mailing list. Click **Next**. -2. Fill out the the **Choose privacy settings** with these options: +2. Fill out the **Choose privacy settings** with these options: | Field | Leads ML value | Members ML value | | --- | --- | --- | diff --git a/communication/marketing-team/role-handbooks/council.md b/communication/marketing-team/role-handbooks/council.md deleted file mode 100644 index ea0e7b8e..00000000 --- a/communication/marketing-team/role-handbooks/council.md +++ /dev/null @@ -1,91 +0,0 @@ -# Marketing Council Handbook - -## Overview - -The Marketing Council is made up of multiple individuals working to bring multiple functions together to ensure Kubernetes contributors have a wealth of robust content and communications. The Marketing Council act as joint leaders to the Upstream Marketing team and its key responsibilities to the entire Kubernetes contributor base. - -#### How It Works - -The ideal Marketing Council is made up of one of each of the leadship roles with one shadow for each. In practice, Council members can cover multiple roles but with the intention of finding someone else to fill the position. Coverage is outlined in the [project README]. - -## Responsibilities - -Responsibilities are categorized by the division of contribution among Marketing Council members. What brings us all together is a commitment to: - -- Be welcoming of everyone by being your unique self -- Be inclusive on contributors, especially non-code contribution -- Be a leader of this sub-project with a commitment to its charter - -#### Program Lead - -- Develop high level marketing strategies and themes to address problem areas, challenges, and innovation/moving the project forward; expected to collaborate with Leads on their strategies for functional areas -- Ensure the team has a unified voice, focus, and work within the charter scope -- Research and identify new and innovative ways of delivering content that appeals to our mission -- Facilitates meetings or can delegate to another Marketing Council member -- Manage the [editorial calendar] and [marketing project] boards -- Coordinate [storytellers] and other member involvement - -#### Promotion Lead - -- Lead and encourage use of owned communication channels, including the team's Twitter account and other social channels -- Helping to recruit other members of the team, ensuring onboarding but delegating to proper lead -- Promoting contributor events - - In the events folder or one off contributor events like SIG onboarding sessions -- KEPs - - To follow the same process as [social guidelines] - - No promotion unless there is an explicit documented request -- Proofreading and editing articles with our [blogging] and [ethos] in mind -- If time allows, market the team; blog about the team and it's progress, encourage team to blog about their work - -#### Liaison Lead - -- Act as or facilitate conversations and workflows between all types of internal stakeholders. This includes attending meetings and coordinating efforts with teams such as: - - SIG Contributor Experience - - Community Group Chairs and Tech Leads - - CNCF - - Steering Committee - - Contributors -- Working with the liaison team members to manage communications and workflows between the groups -- Create new liaison positions as needed to coordinate key initiatives across the Kubernetes community -- Audit the experience of engaging with the Upstream Marketing team and propose opportunities for improvement - -### Minimum Skills and Requirements - -Skills: - -- Be comfortable with general GitHub workflows. To date, this team still requires some expertise in this department to be effective. Current members can teach specifics but a foundation for this role is necessary. You'll be working inside of multiple repositories with different workflows and helping others on the team with troubleshooting. -- Be willing and capable of saying "no" as necessary, but try to get to a "yes, and" to help the community achieve its goals. In short, be empathetic. -- Strong written and verbal communication skills. A willingness to meet (a lot) of new people is important for this work. - -Requirements: - -- Member of the [Kubernetes GitHub Org] -- [Reviewer] in the marketing team folder -- Shadowed under a lead in any role on the team for 6 months total (could be a combination of roles during that time period) - -#### Expected Time Investment - -- Four hours a week as a minimal target. - -#### Duration - -Ideally, no lead should be in the same position indefinitely. With that in mind, every member of the Marketing Council is asked to raise awareness of the position and seek a shadow in preparation of them becoming a lead in the future. The team would like to see new leadership every 12 months to keep a fresh perspective. - -### Becoming a Shadow - -Any Upstream Marketing regular contributor can raise their hand to become a shadow of one or more of the positions in the council. If accepted, the objective of the council members is to nurture that shadow into a leadership position in the next 6 months. - -#### Expectations of a Shadow - -Consistently communicate and collaborate closely with the Marketing Council member of your choice. The objective is to get you, as the shadown, to be a confident leader of the above responsibilities. Be ready to backfill for them when they are unable to attend a meeting or represent the working group. - -[editorial calendar]: https://github.com/orgs/kubernetes/projects/41 -[marketing project]: https://github.com/orgs/kubernetes/projects/39 -[team-resources]: ../team-resources.md -[Kubernetes GitHub Org]: https://git.k8s.io/community/community-membership.md -[Reviewer]: ../OWNERS -[OWNERS]: /communication/OWNERS -[blogging]: ../storytelling-resources/blog-guidelines.md -[ethos]: ../CHARTER.md#ethosvision -[project README]: ../README.md -[storytellers]: ./storytellers.md
\ No newline at end of file diff --git a/communication/marketing-team/storytelling-resources/blog-guidelines.md b/communication/marketing-team/storytelling-resources/blog-guidelines.md deleted file mode 100644 index f756b0f6..00000000 --- a/communication/marketing-team/storytelling-resources/blog-guidelines.md +++ /dev/null @@ -1,65 +0,0 @@ -# Upstream Marketing Blog Guidelines - -This initiative falls under the [Upstream Marketing Charter](./CHARTER.md). - -We are looking for Kubernetes-curious community members who are **interested in writing** and **care about getting the word out** to our huge community of users, developers, and contributors of all types. Here's how to get involved. - -## Requested Content - -We are looking for: - -* TODO << Request specific types of content - -Other types of content, like Kubernetes capabilities and tutorials, are better suited for the [SIG-Docs blogging initiative](/sig-docs/blog-subproject/README.md). - -## Submit a Post - -The quickest way to get involved is to let the team in [#sig-contribex](https://kubernetes.slack.com/archives/C1TU9EB9S) know that you have an idea for an article. - -For now, our official process is to use [SIG-Doc's system](/sig-docs/blog-subproject/README.md). - -## Blogger Expectations, Responsibilities, and Info - -Anyone is welcome to contribute when they have time. - -If you would like to be listed as a member of the team, here are the expectations: - -1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue. -2. Bloggers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active. -3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it. -4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project. - -## How to Write an Effective Blog - -Keep the following points in mind as you write in order to speed up the review process: - -* Use inclusive language understandable by everyone - * Rephrase gendered pronouns (change "he" or "she" to "they" or adjust to remove) - * Remember nothing is simple when you're starting out (remove "just," "simply", and "easy") - * Define terminology or acronyms (do not assume people know what a term means) - * Shy away from jargon and colloquial expressions - * Write clearly and avoid ambiguous sentences -* Emphasize the things you want readers to remember; tell a story - * Stay on topic and stick to the facts - * Design a beginning, middle, and end to your story with a clear call to action - * Provide evidence and data where applicable, to back up your message -* Make the article visually appealing - * Include at least one image (and use public domain or Creative Commons licensed ones) - * Prefer inclusive images like those from [WOCinTech](https://www.flickr.com/photos/wocintechchat/) and [Queer in Tech](https://www.flickr.com/photos/mapbox/albums/72157713100349311) - * Find images on sites like [Creative Commons](https://search.creativecommons.org/), [Pexels](https://www.pexels.com/public-domain-images/), and [Unsplash](https://unsplash.com/images/stock/public-domain)) -* Be accountable and honest as an author - * Remove anything that lacks adequate evidence - * Avoid interjecting personal reactions - * Ensure that the blog post is reviewed by the anyone being mentioned in the piece - * As the author, never talk about your employer, sell, promote, or pitch; this is about upstream community endeavours and the individuals and groups that create it - -## Further Recommendations - -The following are helpful resources for authoring articles: - -* [Creating Quality Content (For Search Engines and People)](https://moz.com/blog/quality-blog-content) -* [How to write effective documentation for your open source project](https://opensource.com/article/20/3/documentation) - -## Review Process - -This process is bootstrapped from the sig-docs blog [subproject](/sig-docs/blog-subproject/README.md). Please ask for review from community liaisons on the sig-docs-blog team or let the team in [#sig-contribex](https://kubernetes.slack.com/archives/C1TU9EB9S) know you need help. diff --git a/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md b/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md index 29247086..df46b73c 100644 --- a/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md +++ b/communication/meeting-notes-archive/201902-201911_Community_Meeting_Notes.md @@ -2320,7 +2320,7 @@ Twitter | [Sep 19th](https://twitter.com/stephenaugustus/status/1174797710043430 * APAC and EU moderators needed the most * Shoutouts * Akutz - Major #shoutout to Katharine Berry (@Katharine) for fixing a UX bug within just a few hours of me mentioning it - [https://kubernetes.slack.com/archives/C09QZ4DQB/p1550863111161400](https://kubernetes.slack.com/archives/C09QZ4DQB/p1550863111161400). Ain’t no service like SIG-Testing service, cause SIG-Testing service don’t stop! - * spiffxp - shoutout to Thomas Runyon (@runyontr) for [https://github.com/kubernetes/kubernetes/pull/72939](https://github.com/kubernetes/kubernetes/pull/72939) allowing us to run eg: `make test-cmd WHAT=deployment` to run just the the deployment cli tests, same sort of thing you can do with `make test` and `make test-integration` + * spiffxp - shoutout to Thomas Runyon (@runyontr) for [https://github.com/kubernetes/kubernetes/pull/72939](https://github.com/kubernetes/kubernetes/pull/72939) allowing us to run eg: `make test-cmd WHAT=deployment` to run just the deployment cli tests, same sort of thing you can do with `make test` and `make test-integration` * bentheelder - shoutout to @gsaenger for writing a wonderful new message for the welcome bot! looking forward to seeing this in more places - ([https://github.com/kubernetes-sigs/contributor-playground/pull/229#issuecomment-466711312](https://github.com/kubernetes-sigs/contributor-playground/pull/229#issuecomment-466711312)) * bentheelder - Shoutout to @jeefy for the really shiny and useful looking structured Kubernetes release notes viewer demo in today's #sig-release meeting, looking forward to seeing more about this! * Maria - shoutout to Silvia Moura Pina (@smourapina) for putting together a workflow to enable the CI signal subteam of the release team keep on top of flagging issues from e2e tests and coordinate follow-ups and to Jorge Alarcon (@Jorge) for spotting an opportunity to offer broader transparency to what the CI signal team is working on, suggesting a structure and kicking off implementation (find current version at [https://github.com/orgs/kubernetes/projects/11](https://github.com/orgs/kubernetes/projects/11)) diff --git a/communication/moderators.md b/communication/moderators.md index 99cd13bd..8bb4874a 100644 --- a/communication/moderators.md +++ b/communication/moderators.md @@ -44,7 +44,6 @@ Administrator seats: 3 | ------------------- | ------------------- | -------- | ------------------------------------------------------- | | Aaron Crickenberger | @spiffxp | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Davanum Srinivas | @dims | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | #### Primary Moderators @@ -175,11 +174,13 @@ Moderators pro tempore seats: 3 ### Owner -Owners seats (non-admin role): 1 +Owners seats (non-admin role): 3 -| Name | Kubernetes Slack ID | Region | Timezone | -| --------------- | ------------------- | -------- | ---------------------------------------------------- | -| Chris Aniszczyk | @caniszczyk | Americas | [CT - Central Time (US Central)](https://time.is/CT) | +| Name | Kubernetes Slack ID | Region | Timezone | +| --------------- | ------------------- | -------- | ---------------------------------------------------- | +| Chris Aniszczyk | @caniszczyk | Americas | [CT - Central Time (US Central)](https://time.is/CT) | +| Bob Killen | @mrbobbytables | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | +| Ihor Dvoretskyi | @ihor.dvoretskyi | Europe | [EET - Eastern European Time](https://time.is/EET) | ### Moderators @@ -193,7 +194,6 @@ Moderators seats: 10 | Jorge Alarcon | @alejandrox1 | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Katharine Berry | @Katharine | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Jaice Singer DuMars | @jdumars | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Noah Kantrowitz | @coderanger | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Ihor Dvoretskyi | @ihor.dvoretskyi | EMEA | [EET - Eastern European Time](https://time.is/EET) | | Yang Li | @idealhack | APAC | [JST - Japan Standard Time](https://time.is/Japan) | @@ -225,7 +225,6 @@ Administrators seats: 6 | Jorge Castro | @castrojo | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Bob Killen | @mrbobbytables | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | | Jorge Alarcon | @alejandrox1 | Americas | [ET - Eastern Time (US East Coast)](https://time.is/ET) | -| Paris Pittman | @paris | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | | Naeil Ezzoueidi | @nzoueidi | EMEA | [CET - Central European Time](https://time.is/CET) | | Yang Li | @idealhack | APAC | [JST - Japan Standard Time](https://time.is/Japan) | | Taylor Dolezal | @onlydole | Americas | [PT - Pacific Time (US West Coast)](https://time.is/PT) | diff --git a/communication/slack-config/OWNERS b/communication/slack-config/OWNERS index 13a52162..ac070da2 100644 --- a/communication/slack-config/OWNERS +++ b/communication/slack-config/OWNERS @@ -8,11 +8,12 @@ approvers: - mrbobbytables - alejandrox1 - jdumars - - parispitmann - coderanger - idvoretskyi - idealhack - munnerz - DylanGraham +emeritus_approvers: + - parispitmann labels: - area/slack-management diff --git a/communication/slack-config/channels.yaml b/communication/slack-config/channels.yaml index a9411546..96dc8d51 100644 --- a/communication/slack-config/channels.yaml +++ b/communication/slack-config/channels.yaml @@ -23,6 +23,9 @@ channels: - name: aus-nz-users - name: awesome-kubernetes - name: aws-authenticator + - name: aws-controllers-k8s + - name: aws-vpc-cni + - name: azure-service-operator - name: bazel - name: bindings-discuss - name: bootkube @@ -60,6 +63,7 @@ channels: - name: cluster-api-kubemark - name: cluster-api-kubevirt - name: cluster-api-nested + - name: cluster-api-nutanix - name: cluster-api-oci - name: cluster-api-openstack - name: cluster-api-operator @@ -83,6 +87,7 @@ channels: - name: csi-secrets-store #this channel is for secrets-store-csi-driver which is a subproject of sig-auth - name: de-events - name: de-users + - name: deppy-dev - name: devfile - name: devspace - name: devstats @@ -90,6 +95,7 @@ channels: - name: digitalocean-k8s - name: distroless - name: diversity + - name: dra - name: draft-dev - name: draft-users - name: eks @@ -106,8 +112,10 @@ channels: - name: events - name: external-dns - name: external-secrets + - name: external-secrets-dev - name: falco - name: fiaas + - name: finops - name: fi-users - name: flatcar - name: flink-operator @@ -191,7 +199,8 @@ channels: - name: kcna-exam-prep - name: klog - name: knative - - name: ko-project + - name: ko-build + id: C01T7DTP65S - name: kompose - name: kong - name: konveyor @@ -211,10 +220,12 @@ channels: - name: krex - name: krustlet - name: kube-aws + - name: kube-bind - name: kube-deploy archived: true - name: kube-monkey - name: kube-oidc-proxy + - name: kube-operating-systems-dev - name: kube-router - name: kube-score - name: kube-spawn @@ -337,6 +348,7 @@ channels: - name: openstack-helm - name: openstack-kolla - name: operator-builder + - name: operator-framework-community - name: operator-sdk-dev - name: ops-status archived: true @@ -346,10 +358,12 @@ channels: - name: pharmer - name: pinniped - name: pl-users + - name: podman-desktop - name: pr-reviews - name: prometheus - name: prometheus-operator - name: prometheus-operator-dev + - name: provider-oci - name: pt_br-users - name: purelb-users - name: raksh @@ -400,13 +414,8 @@ channels: - name: sig-instrumentation - name: sig-multicluster - name: sig-network - - name: sig-node - - name: sig-node-bug-scrub - - name: sig-node-kmm - id: C037RE58RED - - name: sig-node-rkt - archived: true - - name: sig-node-swap + - name: sig-network-multi-network + # sig-node channels are defined in sig-node/ - name: sig-scalability - name: sig-scheduling # sig-security* channels are defined in sig-security/ @@ -432,6 +441,7 @@ channels: - name: suse-caasp - name: talk-proposals - name: tanzu-community-edition + archived: true - name: tanzu-streaming-runtimes - name: terraform-providers - name: terranetes diff --git a/communication/slack-config/restrictions.yaml b/communication/slack-config/restrictions.yaml index 30f97879..b65f837d 100755 --- a/communication/slack-config/restrictions.yaml +++ b/communication/slack-config/restrictions.yaml @@ -27,6 +27,11 @@ restrictions: - path: "sig-network/*.yaml" channels: - "^sig-network-.*$" + - path: "sig-node/*.yaml" + channels: + - "^sig-node" + usergroups: + - "^dra-dev$" - path: "sig-release/*.yaml" channels: - "^sig-release$" diff --git a/communication/slack-config/sig-node/OWNERS b/communication/slack-config/sig-node/OWNERS new file mode 100644 index 00000000..810bc689 --- /dev/null +++ b/communication/slack-config/sig-node/OWNERS @@ -0,0 +1,8 @@ +# See the OWNERS docs at https://go.k8s.io/owners + +reviewers: + - sig-node-leads +approvers: + - sig-node-leads +labels: + - sig/node diff --git a/communication/slack-config/sig-node/config.yaml b/communication/slack-config/sig-node/config.yaml new file mode 100644 index 00000000..72d41ef8 --- /dev/null +++ b/communication/slack-config/sig-node/config.yaml @@ -0,0 +1,8 @@ +channels: + - name: sig-node + - name: sig-node-bug-scrub + - name: sig-node-kmm + id: C037RE58RED + - name: sig-node-rkt + archived: true + - name: sig-node-swap diff --git a/communication/slack-config/sig-node/usergroups.yaml b/communication/slack-config/sig-node/usergroups.yaml new file mode 100644 index 00000000..1de8d274 --- /dev/null +++ b/communication/slack-config/sig-node/usergroups.yaml @@ -0,0 +1,17 @@ +# This file contains a list of all Slack User Groups that are managed by SIG Node. + +usergroups: + - name: dra-dev + long_name: dynamic resource allocation developers + description: Developers working on or with the dynamic resource allocation KEP. + channels: + - sig-node + members: + # Entries are GitHub handles. They must be listed under ../users.yaml. + # Sorted alphabetically! + - bart0sh + - byako + - elezar + - klihub + - klueska # subproject owner + - pohly # subproject owner diff --git a/communication/slack-config/sig-release/usergroups.yaml b/communication/slack-config/sig-release/usergroups.yaml index d53c8b2a..2b3b88d8 100644 --- a/communication/slack-config/sig-release/usergroups.yaml +++ b/communication/slack-config/sig-release/usergroups.yaml @@ -51,15 +51,15 @@ usergroups: - release-notes - sig-release members: - - cici37 # 1.25 Release Team Lead - cpanato # SIG Release Technical Lead - - gracenng # 1.25 RT Lead Shadow - - jeremyrickard # SIG Release Technical Lead / 1.23 Release Team EA - - jlbutler # 1.25 RT Lead Shadow + - gracenng # 1.26 RT Lead Shadow + - jeremyrickard # SIG Release Technical Lead - justaugustus # SIG Release Chair - - leonardpahlke # 1.25 RT Lead Shadow + - katcosgrove # 1.26 RT Lead Shadow + - leonardpahlke # 1.26 RT Lead + - nate-double-u # 1.26 RT Lead Shadow - puerco # SIG Release Technical Lead - - salaxander # 1.25 RT Lead Shadow + - psaggu # 1.26 RT Lead Shadow - saschagrunert # SIG Release Chair # Should match SIG Release Leads at all times: diff --git a/communication/slack-config/sig-security/config.yaml b/communication/slack-config/sig-security/config.yaml index 0b2499dc..1d32525d 100644 --- a/communication/slack-config/sig-security/config.yaml +++ b/communication/slack-config/sig-security/config.yaml @@ -3,4 +3,4 @@ channels: - name: sig-security-assess-capi - name: sig-security-docs - name: sig-security-tooling - + - name: sig-security-assessments diff --git a/communication/slack-config/usergroups.yaml b/communication/slack-config/usergroups.yaml index 10d981df..f814a01a 100644 --- a/communication/slack-config/usergroups.yaml +++ b/communication/slack-config/usergroups.yaml @@ -21,8 +21,8 @@ usergroups: - TaoBeier - name: contributor-comms - long_name: Upstream Marketing - description: Upstream Marketing group. + long_name: Contributor Communications + description: Contributor Communications group. channels: - sig-contribex members: @@ -180,18 +180,28 @@ usergroups: - jonasrosland - pnbrown + - name: podman-desktop-devs + long_name: Podman Desktop Dev Team + description: Active developers of Podman Desktop on #podman-desktop + channels: + - podman-desktop + members: + - cdrage + - benoitf + - vzhukovs + - name: steering-members long_name: Kubernetes Steering Committee description: Members of the Kubernetes Steering Committee channels: - steering-committee members: + - bentheelder - cblecker - - dims + - cpanato - justaugustus - - liggitt - mrbobbytables - - paris + - palnabarun - tpepper - name: grafana-operator-maintainers @@ -208,3 +218,38 @@ usergroups: - robshelly - vladimirmukhin - wurbanski + + - name: devfile-devs + long_name: Devfile Development Team + description: Active developers of Devfile on #devfile + channels: + - devfile + members: + - elsony + - johnmcollier + - kim-tsao + - maysunfaisal + - michael-valdron + - mike-hoang + - rtaniwa + - schultzp2020 + - yangcao77 + + - name: cluster-api-release-team + long_name: Cluster API Release Team + description: Members of the Cluster API Release Team + members: + - alexander-demicev + - aniruddha2000 + - CecileRobertMichon + - cpanato + - dntosas + - furkatgofurov7 + - hackeramitkumar + - joekr + - nawazkh + - oscr + - sayantani11 + - sbueringer + - VibhorChinda + - ykakarap diff --git a/communication/slack-config/users.yaml b/communication/slack-config/users.yaml index 5ddda289..70583cf5 100644 --- a/communication/slack-config/users.yaml +++ b/communication/slack-config/users.yaml @@ -4,28 +4,35 @@ users: adisky: U9YRVLTEH alejandrox1: U6AS37R50 aleksandra-malinowska: U357LUPHS + alexander-demicev: UR7UCR7RV AlexB138: U3JA3MDGV alisondy: U9CBCBLCV ameukam: U68KPQ448 anandrkskd: U01DRS3V0R2 + aniruddha2000: U02BU1RP41H anjaltelang: U028B09KZ5X ankeesler: UBAA1KQ4A annajung: U8SLB1P2Q - AvineshTripathi: U029U44P26B aravindputrevu: U1G27SDU6 asmacdo: UNVH7RY9J Atharva-Shinde: U028J67T478 + AvineshTripathi: U029U44P26B bai: U4XAULHL3 Bart Farrell: U01DZM7PJDT + bart0sh: U8VJC20R3 benjaminapetersen: U0217E7EXV4 + bentheelder: U1P7T516X + benoitf: UCQC3DNUA bhumijgupta: U022JUBM3B4 briandealwis: UAZKM38JV bubblemelon: U7K9C643G + byako: U03GZBD4J4C calebamiles: U1ZDD4CUR camilamacedo86: UJDM393EH castrojo: U1W1Q6PRQ cblecker: U3EDWR9FV cdrage: U2TU9NPH9 + CecileRobertMichon: U98JPHB2M cfryanr: U0188B6J42H chrisshort: U2YGXSD9B cici37: UTY5J12L9 @@ -40,19 +47,24 @@ users: dharmit: U0APPPEKE dims: U0Y7A2MME divya-mohan0209: UV4J7K97Z + dntosas: UKT4D74F3 dougm: U8GG20UE9 + elezar: ULV21K3CH + elsony: UCW8323KL enj: U2T4CVDTJ erismaster: U0162FJ79LY estroz: UKSEANEC9 fabianvf: UAJ3UH29F feiskyer: U0ASA4398 feloy: UFG7CN85U + furkatgofurov7: UV31DL3CG gianarb: U0FSCELCR girishramnani: U9M4K75EU gracenng: U01GX18N6H3 grdryn: U017628HJL8 gsquared94: U0131C0PJBU guineveresaenger: U4H2QU3DW + hackeramitkumar: U045992D532 hasheddan: ULLQEF30C hoegaarden: U7VA4RZS9 hubertstefanski: U01941KQ2UT @@ -72,17 +84,23 @@ users: jlbutler: U0122V3T932 jmccormick2001: UMPLV0G0H jmrodri: U4KATPQ48 + joekr: U02MUT273GA Joel Barker: U014AHSTBPA joelanford: U1R6NQD8W joelsmith: U5SLG8T8F johnbelamaric: U246A1A0N + johnmcollier: UCVS4TNMQ jonasrosland: U0A4G34S2 jrsapi: U0DS2L6E8 justaugustus: U0E0E78AK kadel: U0DE6E8JY kaslin: U5ENKU0AE katharine: UBTBNJ6GL + katcosgrove: U01GDERGEHF kikisdeliveryservice: U9HFFRFT2 + kim-tsao: U02U1LDH4T1 + klihub: U9856A799 + klueska: UF3ARH55Y Kunal Kushwaha: UQ14U3NAY LappleApple: U011C07244F leonardpahlke: U029NBZFV97 @@ -94,27 +112,35 @@ users: markyjackson-taulia: U19TKJ64E MarlonGamez: U016N1XK06R mattmoyer: U0DRP8H42 + maysunfaisal: U01DEHK2YUB mbbroberg: U18JTHMDY micahhausler: U1WJ1BZA5 + michael-valdron: U03LXKVS0SX microwavables: UAF606ESE mik-dass: UCUULSG1W + mike-hoang: U03PDV4LS1Z ming-qiu: U02JVSL5550 mkorbi: UEBLUUA0P mohammedzee1000: U3PFFE8CD MonzElmasry: U018U96HYDQ mrbobbytables: U511ZSKHD munnerz: U0EC03FTN + nate-double-u: U01AWL6BD62 + nawazkh: U03HJN1C81W nikhita: U2PQHGMLN nkubala: UA90QL2BE nzoueidi: UBU72MWP2 onlydole: U1DD4AZND + oscr: U0183J37JUQ pabloschuhmacher: U01AAGZ06KU palnabarun: UBH9NTMBM paris: U5SB22BBQ + psaggu: U012EE74CU8 pb82: U019M8295AQ pensu91: U44FHF81G phenixblue: UB4UVLEAK pnbrown: U011JJTQVGF + pohly: U91901TMF prietyc123: U01D4MBLM52 puerco: ULGHLJ7TP PurneswarPrasad: U027CFKVAB0 @@ -126,11 +152,15 @@ users: rm3l: U034AQUV7PB rnapoles-rh: U01KDAMSWJD robshelly: U01LL4P09SR + rtaniwa: U03K27HLHKN salaxander: UDHV1RXB2 sammy: U8NJFL023 sandipanpanda: U02A47HJ517 saschagrunert: U53SUDBD4 savitharaghunathan: UC8U2V3BM + sayantani11: U028S6XNVSN + sbueringer: U48TE1L75 + schultzp2020: U030K8UQA2G scott-seago: UHGD79E78 sethmccombs: U92LLUZ8A shamus: US7EUUBK8 @@ -152,10 +182,14 @@ users: valaparthvi: U016TMJVDAA varshaprasad96: UK59YP2DA Verolop: U7NNE57PU + VibhorChinda: U031EALE91D vladimirmukhin: UHVSCSD4G + vzhukovs: U030TR1FG85 wilsonehusin: U0100068GF2 wurbanski: URX7CMK97 xmudrii: U4Q2TNGVD xun-jiang: U02J0QC1VKJ + yangcao77: U01D1VCNJQ3 yinw: UMVD1GDCY + ykakarap: U0145EMCA03 zubron: U7G0KNS86 diff --git a/communication/slack-guidelines.md b/communication/slack-guidelines.md index a9f6afa4..45f0e75f 100644 --- a/communication/slack-guidelines.md +++ b/communication/slack-guidelines.md @@ -38,7 +38,7 @@ message) one privately. The Kubernetes Slack Workspace is archived and made available when the administrators have time. There is no explicit interval. -[Slack Archive Download][] +[Slack Archive Download] ### DM (Direct Message) Conversations @@ -100,7 +100,7 @@ determining if you should request a channel: - The channel MUST be Kubernetes related in some way. - Related cloud native projects might be more appropriate on the - [CNCF Slack][]. + [CNCF Slack]. - The project MUST be open source. - Open Source a project BEFORE requesting a channel. We cannot accommodate every organization's open sourcing launch plans. @@ -125,18 +125,18 @@ determining if you should request a channel: project channel is too noisy, but please don't create both at the start. - If you need private discussion areas for security-sensitive topics, a - project-specific Slack or the [CNCF Slack][] may be a better fit. + project-specific Slack or the [CNCF Slack] may be a better fit. - Ask in `#slack-admins` or file an issue if you're unsure It never hurts to ask. ## Requesting a Channel -Channels and User Groups are managed by [Tempelis][], a tool that enables +Channels and User Groups are managed by [Tempelis], a tool that enables external management of Slack. -To add a channel, open a Pull Request (PR) updating the [slack-config][]. +To add a channel, open a Pull Request (PR) updating the [slack-config]. -- Add the channel to 'channels.yaml' following the [Channel Documentation][] +- Add the channel to 'channels.yaml' following the [Channel Documentation] - Channel names must be 21 characters or less in length, limited by Slack design. - Channels must not share the same name with a Slack user or user group. @@ -167,7 +167,7 @@ There are two approvals needed. `/lgtm` and `/approve`. Once one moderator give and add the `/approve` command as well as `/hold cancel`, which will remove the hold on the PR. Once it is signed off and merged, the channel will be created. -For further information, see the [Slack Config Documentation][]. +For further information, see the [Slack Config Documentation]. ### Delegating Channel Ownership @@ -177,9 +177,9 @@ Admins to sign-off on all requests and passes the responsibility to the most relevant group. To delegate channel ownership - Open a Pull Request (PR) updating the -[slack-config][]. +[slack-config]. -- Create a sub-directory under the [slack-config][] for your sig or group. +- Create a sub-directory under the [slack-config] for your sig or group. - Update restrictions.yaml with an entry targeting yaml config files in the sub-directory you created along with one or more regular expressions that match the channel names that should be delegated. @@ -191,7 +191,7 @@ To delegate channel ownership - Open a Pull Request (PR) updating the - "^kubernetes-foo-[a-z]{1,3}$" # channel regexp - example match: kubernetes-foo-bar - "^foo-[a-zA-Z]+$" # channel regexp - example match: foo-awesomechannel ``` -- Create an [OWNERS][] file in the sub-directory adding the appropriate +- Create an [OWNERS] file in the sub-directory adding the appropriate reviewers and approvers for the desired channels. - In the directory create one or more channel configs following the Channel Documentation @@ -211,18 +211,18 @@ For further information, see the ## Requesting a User Group -Channels and User Groups are managed by [Tempelis][], a tool that enables +Channels and User Groups are managed by [Tempelis], a tool that enables external management of Slack. -To add a User Group, open a Pull Request (PR) updating the [slack-config][]. +To add a User Group, open a Pull Request (PR) updating the [slack-config]. - Add the users to users.yaml. **NOTE:** This must be a mapping of their GitHub ID to their Slack Member ID. - To get a person's Slack Member ID, view their profile. Then click on the "**...**" and select **Copy member ID**. It will be a 9 character string of uppercase letters and numbers (example: `U1H63D8SZ`). -- Update [usergroups.yaml][] Follow the guidelines for creating a User Group - in the Slack Config [User Group Documentation][]. +- Update [usergroups.yaml] Follow the guidelines for creating a User Group + in the Slack Config [User Group Documentation]. - In the PR comments, include details on the User Group and `/cc` the members you are adding so that they may sign off and accept being added to the group. @@ -247,7 +247,7 @@ ensure everyone has a great experience. Typically approved requests include: GitHub, CNCF requests, or other tools/platforms used to aid in the management of Slack itself. -- Create a [GitHub Issue][] using the Slack Request template. +- Create a [GitHub Issue] using the Slack Request template. - In the description, describe the request, its intended purpose and benefit to the community. Supplying links to supporting content such as a document outlining what OAuth scopes that are requested and why are **STRONGLY @@ -263,7 +263,7 @@ discussed in Slack itself. ### Admin Expectations and Guidelines Admins should adhere to the general Kubernetes project -[moderation guidelines][]. +[moderation guidelines]. Additionally, admins should ensure they have 2-factor auth enabled for their account and mention they are a Slack admin in the "What I do" portion of their @@ -315,7 +315,7 @@ In general, use your best judgment. Once two Slack admins have reviewed and agreed to sponsor the channel, they will sign off on the Channel Request PR. Once merged, the channel will be created. -Channels managed by [Tempelis][] will automatically have default messages +Channels managed by [Tempelis] will automatically have default messages pinned. For any manually-provisioned channels, such as private channels, add the below message and pin it. @@ -359,7 +359,7 @@ steps. For the reasons listed below, admins may inactivate individual Slack accounts. Due to Slack's framework, it does not allow for an account to be banned or suspended in the traditional sense, merely inactivated. -See [Slack's policy on inactivated accounts][] for more information. +See [Slack's policy on inactivated accounts] for more information. #### Reasons to inactivate an account diff --git a/communication/youtube/OWNERS b/communication/youtube/OWNERS index bb84ded5..3f77586f 100644 --- a/communication/youtube/OWNERS +++ b/communication/youtube/OWNERS @@ -1,7 +1,6 @@ # See the OWNERS docs at https://go.k8s.io/owners reviewers: - - parispittman - jeefy - mrbobbytables - chris-short diff --git a/communication/youtube/youtube-guidelines.md b/communication/youtube/youtube-guidelines.md index e8f2feab..0bd56d03 100644 --- a/communication/youtube/youtube-guidelines.md +++ b/communication/youtube/youtube-guidelines.md @@ -21,15 +21,15 @@ and includes all communications such as YouTube. ## Meeting Playlists -The [Kubernetes YouTube Channel][] has separate playlists for each SIG, WG, UG +The [Kubernetes YouTube Channel] has separate playlists for each SIG, WG, UG meeting recordings, as well as recordings of other recurring events such as the -Kubernetes [community meeting][], [Office Hours][], [Meet our Contributors][] +Kubernetes [community meeting], [Office Hours], [Meet our Contributors] and others. -[Subprojects][], in addition to SIGs, WGs, UGs may request their own playlists +[Subprojects], in addition to SIGs, WGs, UGs may request their own playlists to better target their contributors and increase general discoverability. -To better serve the community, [collaboration][] has been enabled to share the +To better serve the community, [collaboration] has been enabled to share the management of the playlists. Anyone with the appropriate link to the particular playlist can upload videos *to that particular playlist* (links & playlists are one-to-one). @@ -41,9 +41,9 @@ Hours, will be shared with the appropriate point(s) of contact. ### Uploading Guidelines for Collaborators **NOTE:** If you're using a Google Workspace account (formerly known as G Suite) -you may need to [update the permissions in your YouTube settings][]. If you have -any questions, reach out to the [YouTube admins][] or -[SIG Contributor Experience][]. You may need to reach out to someone at your +you may need to [update the permissions in your YouTube settings]. If you have +any questions, reach out to the [YouTube admins] or +[SIG Contributor Experience]. You may need to reach out to someone at your organization if you do not have access to Google Workspace Admin permissions. **NOTE:** Both public and private steering meeting recordings should be made @@ -103,7 +103,7 @@ our governance documents. ### Moderator Expectations and Guidelines Moderators should adhere to the general Kubernetes project -[moderation guidelines][]. +[moderation guidelines]. Moderation responsibilities for YouTube admins is minimal and is centered around checking and removing any potential comments that would violate the @@ -112,7 +112,7 @@ checking and removing any potential comments that would violate the ### Trimming and Editing Recordings -YouTube admins are asked to help [trim][] and [edit][] recordings that come into +YouTube admins are asked to help [trim] and [edit] recordings that come into the video queue. #### Examples: @@ -149,7 +149,7 @@ the steps outlined below. you or reset it to a new one. - Kubernetes YouTube admin permissions - A correctly set up recurring meeting with a start and end time (this is - important) - check [Zoom guidelines][] for more details + important) - check [Zoom guidelines] for more details **Steps:** @@ -166,13 +166,13 @@ the steps outlined below. The following SIGs and groups are currently running splain.io: -- [SIG Auth][] -- [SIG Contributor Experience][] -- [SIG Docs][] -- [SIG Network][] -- [SIG Release][] -- [Steering Committee][] -- [WG Data Protection][] +- [SIG Auth] +- [SIG Contributor Experience] +- [SIG Docs] +- [SIG Network] +- [SIG Release] +- [Steering Committee] +- [WG Data Protection] - The main Zoom admin account which holds Meet Our Contributors and others (if you log in to splain using this account, all of the other accounts will be logged here) @@ -214,9 +214,9 @@ to hear from you. ### Streaming Events YouTube admins with a system capable of streaming may be asked to stream public -Kubernetes Community events such as the weekly [Community Meeting][], -[Office Hours][], [Meet our Contributors][], or other publicly streamed -events. For detailed information about streaming, see our [Streaming Config][]. +Kubernetes Community events such as the weekly [Community Meeting], +[Office Hours], [Meet our Contributors], or other publicly streamed +events. For detailed information about streaming, see our [Streaming Config]. ### Migrating Content @@ -225,7 +225,7 @@ be useful to grab content from other channels. It is currently NOT POSSIBLE to move content from one YouTube channel to another, so the content must be downloaded and then reuploaded to the Kubernetes channel. -1. Download [youtube-dl][], which makes it easier to bulk download videos. +1. Download [youtube-dl], which makes it easier to bulk download videos. 2. Download the channel or playlist with: `youtube-dl <url>` 3. Clean up the filenames as they are used to generate new titles. Do this locally since it is easier than doing it per video in the YouTube web UI. diff --git a/communication/zoom-guidelines.md b/communication/zoom-guidelines.md index 9a5e4858..00df1f0a 100644 --- a/communication/zoom-guidelines.md +++ b/communication/zoom-guidelines.md @@ -5,34 +5,34 @@ description: | --- Zoom is the main video communication platform for Kubernetes. It is used for -running the [community meeting][], [SIG/WG meetings][], [Office Hours][], -[Meet Our Contributors][] and many other Kubernetes online events. Since the Zoom +running the [community meeting], [SIG/WG meetings], [Office Hours], +[Meet Our Contributors] and many other Kubernetes online events. Since the Zoom meetings are open to the general public, a Zoom host or co-host has to moderate a meeting in all senses of the word, from starting and stopping the meeting to -acting on [Kubernetes code of conduct][] issues. +acting on [Kubernetes code of conduct] issues. These guidelines are meant as a tool to help Kubernetes members manage their Zoom resources. -Check the main [moderation][] page for more information on other tools +Check the main [moderation] page for more information on other tools and general moderation guidelines. ## Code of conduct -The Kubernetes project adheres to the [Kubernetes Code of Conduct][] +The Kubernetes project adheres to the [Kubernetes Code of Conduct] throughout all platforms and includes all communication mediums. ## Zoom license management -Zoom licenses are managed by the [CNCF Service Desk][] through the -[Zoom Admins][] listed in the [centralized list of administrators][]. +Zoom licenses are managed by the [CNCF Service Desk] through the +[Zoom Admins] listed in the [centralized list of administrators]. ### Obtaining a Zoom license Ensure that all SIG/WG leads, chairs, and any other necessary trusted owners have access to the `k-sig-<foo>-leads@googlegroups.com` account as described in -the [sig creation procedure][]. Once done, contact one of the [Zoom Admins][] to +the [sig creation procedure]. Once done, contact one of the [Zoom Admins] to obtain a Zoom license. ## Setting up your meeting and moderation @@ -42,9 +42,9 @@ and others who would intentionally attempt to disrupt your Zoom call. To create a meeting with **moderation** enabled, ensure the following: -- Have the [latest version][] of the Zoom client installed. +- Have the [latest version] of the Zoom client installed. - Be logged in as the leads account associated with the meeting **OR** use the - [host key][] to "claim host". + [host key] to "claim host". - Configure a meeting setup through the "Meeting" menu in the leads Zoom account. **NOTE:** Do **NOT** use the "Personal Meeting ID". This will create an "ad-hoc" meeting that is time-bounded and without moderation @@ -64,7 +64,7 @@ After the meeting has started: If you're dealing with a troll or bad actor: - Put the troll or bad actor on **hold**. The participant will be put into a - [waiting room][] and will not be able to participate in the call until the + [waiting room] and will not be able to participate in the call until the host removes the hold. - **NOTE:** Depending on your client version this will be called "**Put in Waiting Room**" instead of on **hold**. @@ -75,7 +75,7 @@ If you're dealing with a troll or bad actor: remove. - After an action has been taken, use the **lock meeting** feature so that no one else can come into the meeting. If that fails, end the call - immediately, and contact the [Zoom Admins][] to report the issue. + immediately, and contact the [Zoom Admins] to report the issue. **NOTE:** You can find these actions when clicking on the **more** or **"..."** options after scrolling over the participants name/information. @@ -83,21 +83,21 @@ options after scrolling over the participants name/information. Hosts **must** be comfortable with how to use these moderation tools and the Zoom settings in general. Make sure whoever is running your meeting is equipped with the right knowledge and skills. If you have any questions or concerns, -reach out to the [Zoom Admins][] and they will be able to provide further +reach out to the [Zoom Admins] and they will be able to provide further guidance and training. #### Related moderation documentation -- Zoom has [documentation on how to use their moderation tools][]. +- Zoom has [documentation on how to use their moderation tools]. - Members of the _leads@_ group have access to an extensive - [best practices doc][] with screenshots going over the community Zoom best + [best practices doc] with screenshots going over the community Zoom best practices. ### Escalating and Reporting a Problem Issues that cannot be handled via normal moderation, or with the assistance of -the [Zoom Admins][] should be escalated to the Kubernetes -[Code of Conduct Committee][] at conduct@kubernetes.io. +the [Zoom Admins] should be escalated to the Kubernetes +[Code of Conduct Committee] at conduct@kubernetes.io. To contact the admin group in Slack, ping `@zoom-admins` in the `#sig-contribex` Slack channel. @@ -105,17 +105,17 @@ Slack channel. ## Meeting recordings Chairs and TLs are responsible for posting all update meetings to their playlist -on YouTube. [Please follow this guideline for more details][]. +on YouTube. [Please follow this guideline for more details]. If a violation has been addressed by a host and it has been recorded by Zoom, -the video should be edited before being posted on the [Kubernetes channel][]. +the video should be edited before being posted on the [Kubernetes channel]. -Contact [SIG Contributor Experience][] if you need help to edit a video +Contact [SIG Contributor Experience] if you need help to edit a video before posting it to the public. ## Screen sharing guidelines and recommendations -Zoom has [documentation on how to use their screen sharing feature][]. +Zoom has [documentation on how to use their screen sharing feature]. Recommendations: @@ -129,7 +129,7 @@ Recommendations: ## Audio/Video quality recommendations While video conferencing has been a real boon to productivity there are still -[lots of things that can go wrong][] during a conference video call. +[lots of things that can go wrong] during a conference video call. There are some things that are just plain out of your control, but there are some things that you can control. Here are some tips if you're just getting into @@ -142,8 +142,8 @@ favor. - **A dedicated microphone** - This is the number one upgrade you can do. Sound is one of those things that can immediately change the quality of your call. If you plan on being here for the long haul, something like a - [Blue Yeti][] will work great due to the simplicity of using USB - audio and having a hardware mute button. Consider a [pop filter][] + [Blue Yeti] will work great due to the simplicity of using USB + audio and having a hardware mute button. Consider a [pop filter] as well if necessary. - **A Video Camera** - A bad image can be worked around if the audio is good. Certain models have noise canceling dual-microphones, which are a great @@ -165,7 +165,7 @@ for which models work best. ### Pro-tips -- [Join on muted audio and video][] in order to prevent noise to those +- [Join on muted audio and video] in order to prevent noise to those already in a call. - If you don't have anything to say at that moment, **MUTE**. This is a common problem. You can help out a teammate by mentioning it on Zoom chat or |