From 0f378954cb387ff4d346153a68ac7458cf484b7d Mon Sep 17 00:00:00 2001 From: Matthew Broberg Date: Fri, 3 Sep 2021 11:53:00 -0500 Subject: Contributor Comms reorganization Significant clean up effort for Upstream Marketing documentation focused on: - Ensure roles described how the team has functioned over the last year - Fill in stale TODOs with solid information - Organize resources into the storytelling folder Signed-off-by: Matthew Broberg --- committee-steering/governance/sig-governance.md | 4 +- communication/marketing-team/CHARTER.md | 28 +++---- communication/marketing-team/README.md | 43 ++++------ communication/marketing-team/blog-guidelines.md | 65 ---------------- communication/marketing-team/event-checklist.md | 7 -- .../marketing-team/multichannel-communications.md | 87 --------------------- .../marketing-team/role-handbooks/council.md | 91 ++++++++++++++++++++++ .../marketing-team/role-handbooks/editor.md | 78 ------------------- .../role-handbooks/internal-marketing.md | 47 ----------- .../marketing-team/role-handbooks/social-media.md | 25 ------ .../marketing-team/role-handbooks/storytellers.md | 29 +++---- .../marketing-team/role-handbooks/wip-roles.md | 13 ---- communication/marketing-team/social-guidelines.md | 89 --------------------- .../storytelling-resources/blog-guidelines.md | 65 ++++++++++++++++ .../storytelling-resources/event-checklist.md | 7 ++ .../multichannel-communications.md | 87 +++++++++++++++++++++ .../storytelling-resources/social-guidelines.md | 89 +++++++++++++++++++++ 17 files changed, 383 insertions(+), 471 deletions(-) delete mode 100644 communication/marketing-team/blog-guidelines.md delete mode 100644 communication/marketing-team/event-checklist.md delete mode 100644 communication/marketing-team/multichannel-communications.md create mode 100644 communication/marketing-team/role-handbooks/council.md delete mode 100644 communication/marketing-team/role-handbooks/editor.md delete mode 100644 communication/marketing-team/role-handbooks/internal-marketing.md delete mode 100644 communication/marketing-team/role-handbooks/social-media.md delete mode 100644 communication/marketing-team/role-handbooks/wip-roles.md delete mode 100644 communication/marketing-team/social-guidelines.md create mode 100644 communication/marketing-team/storytelling-resources/blog-guidelines.md create mode 100644 communication/marketing-team/storytelling-resources/event-checklist.md create mode 100644 communication/marketing-team/storytelling-resources/multichannel-communications.md create mode 100644 communication/marketing-team/storytelling-resources/social-guidelines.md diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 1b402b8b..b9dbadb0 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -179,7 +179,7 @@ Example of SIG roles created to help operations: - [Production Readiness Reviewer] - [Events Lead] - [PR Wrangler] -- [Editor] +- [Marketing Council] Other roles... - *MUST* be tracked on the SIGs README with a link to the role definition @@ -273,7 +273,7 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [The Release Team: Bug Triage, CI Signal, and more]: https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks [Production Readiness Reviewer]: https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#becoming-a-prod-readiness-reviewer-or-approver [API Reviewer and Moderator]: https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md#expanding-the-reviewer-and-approver-pool -[Editor]: https://github.com/kubernetes/community/blob/master/communication/marketing-team/role-handbooks/editor.md +[Marketing Council]: https://github.com/kubernetes/community/blob/master/communication/marketing-team/role-handbooks/council.md [Events Lead]: https://github.com/kubernetes/community/blob/master/events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ [monthly community meeting]: /events/community-meeting.md diff --git a/communication/marketing-team/CHARTER.md b/communication/marketing-team/CHARTER.md index 2ada76e0..ff6da58e 100644 --- a/communication/marketing-team/CHARTER.md +++ b/communication/marketing-team/CHARTER.md @@ -1,16 +1,16 @@ -# Kubernetes Upstream Marketing Team Charter +# Kubernetes Upstream Marketing Contributor Communications Team Charter ## Summary -The mission of the Kubernetes Upstream Marketing Team is to elevate the hard work being done throughout the Kubernetes community by its contributors. Promoting the work and helping fill the needs of the Kubernetes community is the driving force behind the Kubernetes Upstream Marketing Team. The goal of this work is to improve the overall sustainability of the project by giving or elevating information to contributors so they stay well informed. +The mission of the Kubernetes Upstream Marketing Contributor Communications team (Contributor Comms for short) is to elevate the hard work being done throughout the Kubernetes community by its contributors. Promoting the work and helping fill the needs of the Kubernetes community is the driving force behind the Contributor Comms team. The goal of this work is to improve the overall sustainability of the project by giving or elevating information to contributors so they stay well informed. ## Ethos/Vision -This group's work is in support of the upstream Kubernetes community (the open source project). As such it will adhere to the [Kubernetes Community Values](/values.md#kubernetes-community-values). The core value we feel strongest about is [Community over product or company](/values.md#community-over-product-or-company). The makeup of this team will be from all walks of life including vendors. The work of the Kubernetes community should always be prioritized over vendor created works. Kubernetes Upstream Marketing Team members are expected to act in the interest of the community and not their employers. +This group's work is in support of the upstream Kubernetes community only (the open source project). As such it will adhere to the [Kubernetes Community Values](/values.md#kubernetes-community-values). The core value we feel strongest about is [Community over product or company](/values.md#community-over-product-or-company). The makeup of this team will be from all walks of life including vendors. The work of the Kubernetes community should always be prioritized over vendor created works. Contributor Comms team members are expected to act in the interest of the community and not their employers. ## Goals -The goal of the Kubernetes Upstream Marketing Team is to be of service to the community. It will act to facilitate conversations across the Kubernetes community. It will also act as a voice of the community to broaden the reach and effectiveness of community communications. Facilitating those communications is a critical function of this team. +The goal of the Contributor Comms team is to be of service to the community by being leaders in contributor storytelling. It will act to facilitate conversations across the Kubernetes community and share compelling stories about contributors. It will also act as a voice of the community to broaden the reach and effectiveness of community communications. Facilitating those communications is a critical function of this team. ## Out of Scope @@ -18,28 +18,22 @@ This team operates independently from Cloud Native Computing Foundation (CNCF) o ## Governance -TODO +Leadership is divided up between [Marketing Council] team members. This group of leaders divide up the core responsibilities of the team and look to further optimize the experience of both code and non-code contributors. ### Roles -* Internal Comms -* Social Media -* Web/Blog - -All roles should have at least one shadow. All leads should actively recruit shadows for the entire team. - -TODO +Roles are divided up between Marketing Council members and other members, notably Storytellers. Marketing Council members are scoped to have at least one shadow. All leads should actively recruit shadows for the entire team. ### Decision Making --lazy consensus (policy) +Decisions affecting all of Contributor Comms are made primarily led by the program lead as defined in the [Marketing Council]. They come to decision by lazy consensus with the goal of everyone getting a say, but they are responsible for making the decision. If other council members do not agree with one or more decisions made on behalf of the team, this should be raised to the advisors as well as the SIG Contributor Experience leads to facilitate a resolution. --leads make calls on smaller editorial and transactional (example: twitter) - -TODO +Other council leads have the responsibility and autonomy to decide what is right for their portion of the council's division of work. The same escalation path can be used in case of disagreement that cannot be resolved by internal discussion. ### Off-Ramp Things change, priorities get optimized, life happens. Having an easy on and off ramp is important to this team. If a lead needs to take an extended absence or leave the team, a shadow would be offered the lead position prior to seeking a lead elsewhere. Therefore moving from shadow to lead and vice versa should be made as simply as possible by continued communications from this team about its members, roles, successes, and failures. -(quit/leave/boot) +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]: ../role-handbooks/council.md \ No newline at end of file diff --git a/communication/marketing-team/README.md b/communication/marketing-team/README.md index 4dc74f8c..6094aaa2 100644 --- a/communication/marketing-team/README.md +++ b/communication/marketing-team/README.md @@ -1,41 +1,29 @@ -# Contributor Marketing +# Upstream Marketing -The Contributor Marketing Team is part of the community-management subproject in +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. ## Purpose -To better inform the Kubernetes contributor community and highlight their work to -the broader ecosystem. +To better inform the Kubernetes contributor community and highlight their work to the broader ecosystem. -| Area & Handbook Link | Lead | Team | Notes | -| --- | --- | --- | --- | -| [Editorial] | editor: @mbbroberg | assoc editor: [Could be you!] | advisor: @parispittman | -| [Internal Communications] | @rajula96reddy | [Could be you!] | | -| [Social Media] | @kaslin | [Could be you!] | advisors: @parispittman,@chris-short | -| [Storytellers] | liaison to sig-docs-blog team @onlydole | @celanthe, @vonguard, @boluisa, @kaslin, @divya-mohan0209, and [Could be you!] | | -| [Designer] | [Could be you!] | | help us with digital assets, infographics, contributor site | -| APAC Liaison | @pensu91 | [Could be you!] | | +| Area & Handbook Link | Team | Notes | +| --- | --- | --- | +| [Marketing Council] | program lead: @mbbroberg, program shadow: @JasonMorgan, promotion lead: @kaslin, liaison lead: @rajula96reddy | advisors: @parispittman, @chris-short. We always need more shadows! Reach out if interested. | +| [Storytellers] & other members | @kunal-kushwaha, @gkarthiks, @dewan-ahmed, @joelbyronbarker, Sladyn Nunes | New to Contributor Comms? Add your name here! +| Liaisons | release: @rajula96reddy, docs: `OPEN` | need support from Contributor Comms? Ping the liaison lead. ## Contact Us! -- Reach out to an individual above via slack -- Whole group - @contributor-comms in #sig-contribex on slack +- Reach out to an individual above via Slack + - Ping the whole team: @contributor-comms in #sig-contribex on slack - Tag us in an issue in [kubernetes/community] with the label [area/contributor-comms] -- Set a marketing issue template in [kubernetes/community] -- Follow us on @K8sContributors on Twitter + - Set a marketing issue template in [kubernetes/community] +- Follow us on @K8sContributors on [Twitter] -## Focus Areas +## Join us! -1. Inter-community group comms/project-wide contributor communications -2. Contributor twitter/social and web (contributor site) -3. Blogging (work happening in SIGs, stories about contributors, recaps) -4. Program and event promotion (community meeting, meet our contributors, steering - election, et al) - -## Could be you! - -We still have many roles available! +We are always open to being a home for contributors to Kubernetes whether you code or not. * Come to one of our [meetings] (Every Friday at 8am PT). See the [calendar] to add it to your own calendar. * Join our [mailing-list], and/or reach out to us on the #sig-contribex channel on the Kubernetes slack ([slack.k8s.io](http://slack.k8s.io)). @@ -48,10 +36,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 -[Editorial]: ./role-handbooks/editor.md +[Marketing Council]: ./role-handbooks/editor.md [Internal Communications]: ./role-handbooks/internal-marketing.md [Social Media]: ./role-handbooks/social-media.md [Storytellers]: ./role-handbooks/storytellers.md [Designer]: ./role-handbooks/wip-roles.md [kubernetes/community]: https://github.com/kubernetes/community/issues [area/contributor-comms]: https://github.com/kubernetes/community/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fcontributor-comms +[Twitter]: https://twitter.com/K8sContributors/ \ No newline at end of file diff --git a/communication/marketing-team/blog-guidelines.md b/communication/marketing-team/blog-guidelines.md deleted file mode 100644 index f756b0f6..00000000 --- a/communication/marketing-team/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/marketing-team/event-checklist.md b/communication/marketing-team/event-checklist.md deleted file mode 100644 index 48549da4..00000000 --- a/communication/marketing-team/event-checklist.md +++ /dev/null @@ -1,7 +0,0 @@ -TODO - this document is intended to outline all Contributor Communications team activities to support a major event, like KubeCon. Please add to the list as we learn. See the [Marketing Team README](./README.md) for info on the team. - -# Pre-Event (KubeCon) Checklist - -* Email to k-dev about maintainer sessions, meet the maintainer, peer group mentoring, etc. (Example: https://groups.google.com/g/kubernetes-dev/c/FDwGepXJK5s/m/kOwtU7X2BwAJ) -* Tweets about maintainer sessions throughout the week -* diff --git a/communication/marketing-team/multichannel-communications.md b/communication/marketing-team/multichannel-communications.md deleted file mode 100644 index ac457c62..00000000 --- a/communication/marketing-team/multichannel-communications.md +++ /dev/null @@ -1,87 +0,0 @@ -# Multichannel communications - -The goal of this is to provide a clearer way for community members to share and consume Kubernetes information. - -## Motive - -Our motive is as follows: - -* Provide all Kubernetes contributors with a dependable experience of communication to and from the project -* Find ways of adding our human touch to potentially overwhelming quantities of information -* Provide clear expectations on what’s important, urgent, or otherwise -* Build process like we build Kubernetes, so that our contributors understands it, and it works well at scale - -## Outbound and inbound communications - -All outbound communications will have a single source of truth in kubernetes-dev@googlegroups.com. - -Justification for this canonical location: - -* Per 2018 and 2019 survey results, it has grown in popularity as the one place to check for contributor news -* Highlighted in the contributor guide, SIG READMEs, governance documentation, and many other places - -All other communication channels will point to that canonical location because we want to: - -* Avoid having many places with partial information -* Avoid community member's needing to follow multiple places -* Avoid confusion on where to get the right information -* Create an easier process for information sharing - -## Mapping Type to Tier - -We have identified four (4) different tiers of information: - -* **Action Required** - * Participation is critical to the Kubernetes project and has a firm due date - * Example 1: The Contributor Survey responses are due by $date - * Example 2: Code freeze is at $date, get your code in! - * Other release information should go through the release team -* **Priority Information** - * Critical information to productive participation and community sustainability - * Example 1: Updates on an upcoming steering committee election - * Example 2: Changes in workflows, issue triaging, etc -* **Feedback Appreciated** - * When participation is helpful, but not required by everyone in order to be successful - * Example: Kubernetes Enhancement Proposals (KEPs) -* **In case you missed it (ICYMI)** - * Information that is not urgent or priority, but will be interesting to others and worthwhile to highlight - * Example: The monthly community & mentors meeting schedule - -Based on these tiers, communication will flow through different channels and may be repeated as necessary. - -## Channels of communication - -These channels will be used for written communication and tips for using them effectively: - -* kubernetes-dev@googlegroups.com - * Single source of truth - * Make sure you're not burying the lead, action items should be clearly stated -* Slack - * Short blurb in related channels (see below) about the information on k-dev, linking to the canonical post -* Discourse - * Short blurb in the related category about the information on k-dev, linking to the canonical post -* Twitter - * Fire hose of information in 280 characters or fewer; items can be covered more than once - -## Slack channels to be used - -As Slack is a massive workspace for us it can sometimes be hard to know exactly where to put information. Here is the current list of contributor-focused channsl that we will post information to: - -* #contributor-summit -* #meet-our-contributors -* #chairs-and-techleads - -Regional channels: - -* emea-dev (EMEA) -* in-dev (India) -* jp-dev (Japan) -* cn-dev (China) -* kr-dev (Korea) -* aus-nz-dev (Australia & New Zealand) - -To find SIG-specific channels, check the Contact column in the [SIG list](https://github.com/kubernetes/community/blob/master/sig-list.md) - -## Questions? - -Have a question about what's written here or something else? Reach out to the [marketing team](README.md)! diff --git a/communication/marketing-team/role-handbooks/council.md b/communication/marketing-team/role-handbooks/council.md new file mode 100644 index 00000000..9a2f1979 --- /dev/null +++ b/communication/marketing-team/role-handbooks/council.md @@ -0,0 +1,91 @@ +# 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, Coucil 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/role-handbooks/editor.md b/communication/marketing-team/role-handbooks/editor.md deleted file mode 100644 index 3e15e13f..00000000 --- a/communication/marketing-team/role-handbooks/editor.md +++ /dev/null @@ -1,78 +0,0 @@ -# Editor Handbook - -## Overview - -The Editor takes on a beacon role for the group to bring multiple functions together ensuring Kubernetes contributors have a wealth of robust content and communications. - -### Responsibilities - -- 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 Associate Editor -- Manage the [editorial calendar] and [marketing project] boards. -- Proofreading and editing articles with our [blogging] and [ethos] in mind -- Act as or facilitate conversations and workflows between all types of stakeholders: - - 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 -- Helping to recruit other members of the team, ensuring onboarding but delegating to proper lead; fall back when no lead present is the Editor -- Has the ability to modify the team charter and seeks consensus with Contributor Experience communication [OWNERS] when considering any major changes. -- If time allows, market the team; blog about the team and it's progress, encourage team to blog about their work - -### Minimum Skills and Requirements - -Skills: - -- Be comfortable with general GitHub workflows. We can teach you ours but a foundation for this role is necessary. You'll be working inside of multiple repositories with different experiences and helping others on the team with troubleshooting. -- Strong written and verbal skills -- Be ok with saying no, but with a reason to back it up; be empathetic. -- Have existing relationships with the contributor community either through other work or as an Associate Editor -- Patience - -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. - -### Platforms, Tools, Access - -Here is a checklist of items we will work to get access when you accept the role. - -- Access to send and respond to email from community@kubernetes.io -- Access to community and website repositories, all relevant calendars, and project boards -- Other items listed in [team-resources] - -### Duration - -6months to 12months?? -//discussion point - -## Associates Overview (Shadow) - -The Associate Editor should be able to achieve the above list of skills by the time they will be eligible to become the lead. - -### Expectations - -Collaborate closely with the lead Editor toward the responsibilities outlined above. Be ready to backfill for them when they are unable to attend a meeting or represent the working group. - -TODO - -[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]: ../blog-guidelines.md -[ethos]: ../CHARTER.md#ethosvision diff --git a/communication/marketing-team/role-handbooks/internal-marketing.md b/communication/marketing-team/role-handbooks/internal-marketing.md deleted file mode 100644 index 1fe87e9e..00000000 --- a/communication/marketing-team/role-handbooks/internal-marketing.md +++ /dev/null @@ -1,47 +0,0 @@ -# Internal Communications and Marketing Handbook - -## Overview - -The Internal communications role is responsible for handling communications out to the broader Kubernetes contributor community. The types of communications are outlined in our [multichannel communications doc]. - -## Responsibilities - -- Working towards a more streamlined communication process within the project for different use cases -- Create and maintain a one stop shop intake form/issue template/etc for contributors to get comms and marketing support -- Identifying communication milestones and deadlines -- Map out communication pipelines -- 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 - -## Minimum Skills and Requirements - -- Are a member of the [Kubernetes GitHub Org] -- Shadowed in this role or another role on the marketing team for at least 3 months - -### Expected Time Investment - -3-5 hours a week - -### Platforms, Tools, and Access - -- Needs access to send and respond to mail on community@kubernetes.io -- Contributor calendar -- and everything listed in [team-resources] - -## Associates Overview (Shadow) - -The Internal Communicaitons Shadow should be able to achieve the above list of skills by the time they will be eligible to become the lead. - -## Out of scope - -- release; there is a communications coordinator (can help where needed, be an advisor, or help with reach) -- contributor summit; there is a role that will assume a communications function (can help where needed, be an advisor, or help with reach) -- community meetings; there is already a well-defined process in place where each month's lead manage communications out to the community - -[multichannel communications doc]: ../multichannel-communications.md -[social guidelines]: ../social-guidelines.md -[team-resources]: ../team-resources.md -[Kubernetes GitHub Org]: https://git.k8s.io/community/community-membership.md diff --git a/communication/marketing-team/role-handbooks/social-media.md b/communication/marketing-team/role-handbooks/social-media.md deleted file mode 100644 index e75efe63..00000000 --- a/communication/marketing-team/role-handbooks/social-media.md +++ /dev/null @@ -1,25 +0,0 @@ -# Social Media Handbook - -## Overview - -TODO - -## Minimum Skills and Requirements - -- Are a member of the [Kubernetes GitHub Org] -- Familiar with twitter by either having a personal account or managing another account (brand, oss project, employer, local nonprofit, etc) -- TODO - -### Expected Time Investment - -TODO -3-5 hours a week - -## General Expectations - -- Most of this information can be found in our [social guidelines] -- Be welcoming, be yourself - -## Associates Overview (Shadow) - -TODO diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/marketing-team/role-handbooks/storytellers.md index f4f59c2e..1d0c330f 100644 --- a/communication/marketing-team/role-handbooks/storytellers.md +++ b/communication/marketing-team/role-handbooks/storytellers.md @@ -2,25 +2,23 @@ ## Overview -It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok - it's not there to put on a circus but provide valuable information and get you were you need to go. +Upstream Marketing depends on great storytelling to get the message out about our amazing community. -In this role, Storytellers are here for both! Storytellers will take us on journeys through words and visuals to help us craft... -TODO add more here +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. + +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 ⚡️ -TODO -document a short workflow here -1 should be for those who are comfortable going back and forth on a PR -another option should include agreeing on a *final* version in a separate -collaborative doc tool and the sig-docs-liaison or Editor will start the PR -process +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]. + +Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder]. -## Minimum Skills and Experience +## Minimum Skills and Requirements - Have a passion for telling stories, technical writing, journalism, and painting pictures with words - Desire to be a Kubernetes Org Member and if not already, work your way towards membership -- Comfortable with working with GitHub workflows or working in a collaborative doc tool with the Editor +- Helpful but not required: Comfortable with working with GitHub workflows or working in a collaborative document like Hackmd.io ## Expectations @@ -33,6 +31,9 @@ If you would like to be listed as a member of the team, here are the expectation 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. -There is no shadow roles for Storytellers. If Storytellers are interested in -becoming the teams sig-docs-liaison they should follow the process for the -community role on the sig-docs-blog team. TODO add link here +There is no shadow roles for Storytellers. If Storytellers are interested in becoming a shadow they can read more about it in the [Marketing Council Handbook]. + +[blogging guidelines]: ../storytelling-resources/blog-guidelines.md +[YouTube guidelines]: /communication/youtube/youtube-guidelines.md +[storytelling resources folder]: ../storytelling-resources/ +[Marketing Council Handbook]: ../council.md \ No newline at end of file diff --git a/communication/marketing-team/role-handbooks/wip-roles.md b/communication/marketing-team/role-handbooks/wip-roles.md deleted file mode 100644 index a1d477f3..00000000 --- a/communication/marketing-team/role-handbooks/wip-roles.md +++ /dev/null @@ -1,13 +0,0 @@ -# Work In Progress Roles - -## Purpose - -Capture roles that we would like to have but don't have them filled for Reasons. - -## Roles - -1. Designer -someone to help with youtube thumbnails, logos, social clips/gifs -help us manage digital assets - -2. TODO / Add one here diff --git a/communication/marketing-team/social-guidelines.md b/communication/marketing-team/social-guidelines.md deleted file mode 100644 index 6871ceb6..00000000 --- a/communication/marketing-team/social-guidelines.md +++ /dev/null @@ -1,89 +0,0 @@ -# Social media guidelines - -**Twitter:** [K8sContributor](https://twitter.com/k8scontributors) - -## 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. - -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. - -Attempt to keep abbreviations to a minimum. Things like `k/k`, for example, might be known in the community, but for new contributors, this is something that is learned with time. Minimizing abbreviations and using plain language is strongly encouraged. - -Responses should include helpful links, validation, and/or additional information. Responses should occur within 48 hours. At the very least, like things as an acknowledgment. Sources of information should include Kubernetes contributor related web properties and documentation: kubernetes/community and kubernetes/website. You can't go wrong linking to an official Kubernetes repo. - -Ideally, no individuals outside of the contributor community, with the possible exception that they are talking about contributors, should be an considered a topic of messaging. Example: Bill Gates isn't part of the Kubernetes community, so tweets with @BillGates will not be published. - -Other CNCF projects, unless there is a common contributor cause, are out of scope for coverage by this team's social media accounts. - -Kubernetes Organization Members with access to account are: - -- @kaslin -- @parispittman -- @mrbobbytables -- @chris-short -- @mbbroberg - -The official Social Media Lead is listed on the [team resources page](README.md). - -## Themes/Topics -The focus should be on topics that will be of interest to upstream contributors. - -- Contributor/SIG blog posts -- Contributor events -- Process changes -- Release info, code freeze, et al -- Accomplishments (reaching 100,000 GitHub stars for example) -- Significant historical events as related to the project (Kubernetes birthday, previous events, etc.) -- Steering Committee Announcements -- Contributor guide/dev guide updates -- Work coming out of SIG-Contributor Experience - -Examples of topics that this group does NOT focus on include: - -- Content targeted at downstream users such as: - - Getting started with Kubernetes - - Best practices for running in production - -### Example Social Media - -- Weekly on Sunday: Link with community calendar and "This week in upstream community group meetings..." -- As they come in: - - Emails from k-dev - - #Shoutouts (from #shoutouts slack channel; try to include social handles or github handles if possible) - - Requests from issue templates -- Scheduled launches - - Your upcoming blog posts - - Requests from issue templates -- Every Wednesday (example) - - New contributor Wednesday - tweet a bunch of good-first-issue label GitHub issues (TODO: Automate) -- Event support: - - (with information from the issue template) - - Examples: Steering Committee voting will need a reminder weekly for at least a month - - Meet our contributors should have a reminder 3 days before the event and then 30 minutes before on the day of - -## KEPs - -([Kubernetes Enhancement Proposals]) - -### Ground Rules - -- The social media team cannot tweet KEPs at this time. -- This may change if we can get a few owner(s)/group who can approve them -- This guideline can only change with Steering, SIG-Arch, and SIG-Release approval - -### Frequently Asked Questions (FAQ) - -Q: Will the account follow other accounts? - -A: TODO (Y/N). The account is designed for information dissemination, so we will focus on that by (following no one and focusing on sharing || following everyone to extend our reach). - -Q: Do we engage with hostile messages? - -A: No. Don't feed the trolls. Mute them is the correct response. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](/code-of-conduct.md). The community is focused on openness and our accounts should be too, but there are times when we should reduce harmful people's visibility through blocking. - -Credit: [Fedora Community](https://fedoraproject.org/wiki/Marketing) - - -[#KEPs]: (#KEPs) -[Kubernetes Enhancement Proposals]: https://github.com/kubernetes/enhancements/tree/master/keps diff --git a/communication/marketing-team/storytelling-resources/blog-guidelines.md b/communication/marketing-team/storytelling-resources/blog-guidelines.md new file mode 100644 index 00000000..f756b0f6 --- /dev/null +++ b/communication/marketing-team/storytelling-resources/blog-guidelines.md @@ -0,0 +1,65 @@ +# 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/marketing-team/storytelling-resources/event-checklist.md b/communication/marketing-team/storytelling-resources/event-checklist.md new file mode 100644 index 00000000..48549da4 --- /dev/null +++ b/communication/marketing-team/storytelling-resources/event-checklist.md @@ -0,0 +1,7 @@ +TODO - this document is intended to outline all Contributor Communications team activities to support a major event, like KubeCon. Please add to the list as we learn. See the [Marketing Team README](./README.md) for info on the team. + +# Pre-Event (KubeCon) Checklist + +* Email to k-dev about maintainer sessions, meet the maintainer, peer group mentoring, etc. (Example: https://groups.google.com/g/kubernetes-dev/c/FDwGepXJK5s/m/kOwtU7X2BwAJ) +* Tweets about maintainer sessions throughout the week +* diff --git a/communication/marketing-team/storytelling-resources/multichannel-communications.md b/communication/marketing-team/storytelling-resources/multichannel-communications.md new file mode 100644 index 00000000..ac457c62 --- /dev/null +++ b/communication/marketing-team/storytelling-resources/multichannel-communications.md @@ -0,0 +1,87 @@ +# Multichannel communications + +The goal of this is to provide a clearer way for community members to share and consume Kubernetes information. + +## Motive + +Our motive is as follows: + +* Provide all Kubernetes contributors with a dependable experience of communication to and from the project +* Find ways of adding our human touch to potentially overwhelming quantities of information +* Provide clear expectations on what’s important, urgent, or otherwise +* Build process like we build Kubernetes, so that our contributors understands it, and it works well at scale + +## Outbound and inbound communications + +All outbound communications will have a single source of truth in kubernetes-dev@googlegroups.com. + +Justification for this canonical location: + +* Per 2018 and 2019 survey results, it has grown in popularity as the one place to check for contributor news +* Highlighted in the contributor guide, SIG READMEs, governance documentation, and many other places + +All other communication channels will point to that canonical location because we want to: + +* Avoid having many places with partial information +* Avoid community member's needing to follow multiple places +* Avoid confusion on where to get the right information +* Create an easier process for information sharing + +## Mapping Type to Tier + +We have identified four (4) different tiers of information: + +* **Action Required** + * Participation is critical to the Kubernetes project and has a firm due date + * Example 1: The Contributor Survey responses are due by $date + * Example 2: Code freeze is at $date, get your code in! + * Other release information should go through the release team +* **Priority Information** + * Critical information to productive participation and community sustainability + * Example 1: Updates on an upcoming steering committee election + * Example 2: Changes in workflows, issue triaging, etc +* **Feedback Appreciated** + * When participation is helpful, but not required by everyone in order to be successful + * Example: Kubernetes Enhancement Proposals (KEPs) +* **In case you missed it (ICYMI)** + * Information that is not urgent or priority, but will be interesting to others and worthwhile to highlight + * Example: The monthly community & mentors meeting schedule + +Based on these tiers, communication will flow through different channels and may be repeated as necessary. + +## Channels of communication + +These channels will be used for written communication and tips for using them effectively: + +* kubernetes-dev@googlegroups.com + * Single source of truth + * Make sure you're not burying the lead, action items should be clearly stated +* Slack + * Short blurb in related channels (see below) about the information on k-dev, linking to the canonical post +* Discourse + * Short blurb in the related category about the information on k-dev, linking to the canonical post +* Twitter + * Fire hose of information in 280 characters or fewer; items can be covered more than once + +## Slack channels to be used + +As Slack is a massive workspace for us it can sometimes be hard to know exactly where to put information. Here is the current list of contributor-focused channsl that we will post information to: + +* #contributor-summit +* #meet-our-contributors +* #chairs-and-techleads + +Regional channels: + +* emea-dev (EMEA) +* in-dev (India) +* jp-dev (Japan) +* cn-dev (China) +* kr-dev (Korea) +* aus-nz-dev (Australia & New Zealand) + +To find SIG-specific channels, check the Contact column in the [SIG list](https://github.com/kubernetes/community/blob/master/sig-list.md) + +## Questions? + +Have a question about what's written here or something else? Reach out to the [marketing team](README.md)! diff --git a/communication/marketing-team/storytelling-resources/social-guidelines.md b/communication/marketing-team/storytelling-resources/social-guidelines.md new file mode 100644 index 00000000..6871ceb6 --- /dev/null +++ b/communication/marketing-team/storytelling-resources/social-guidelines.md @@ -0,0 +1,89 @@ +# Social media guidelines + +**Twitter:** [K8sContributor](https://twitter.com/k8scontributors) + +## 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. + +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. + +Attempt to keep abbreviations to a minimum. Things like `k/k`, for example, might be known in the community, but for new contributors, this is something that is learned with time. Minimizing abbreviations and using plain language is strongly encouraged. + +Responses should include helpful links, validation, and/or additional information. Responses should occur within 48 hours. At the very least, like things as an acknowledgment. Sources of information should include Kubernetes contributor related web properties and documentation: kubernetes/community and kubernetes/website. You can't go wrong linking to an official Kubernetes repo. + +Ideally, no individuals outside of the contributor community, with the possible exception that they are talking about contributors, should be an considered a topic of messaging. Example: Bill Gates isn't part of the Kubernetes community, so tweets with @BillGates will not be published. + +Other CNCF projects, unless there is a common contributor cause, are out of scope for coverage by this team's social media accounts. + +Kubernetes Organization Members with access to account are: + +- @kaslin +- @parispittman +- @mrbobbytables +- @chris-short +- @mbbroberg + +The official Social Media Lead is listed on the [team resources page](README.md). + +## Themes/Topics +The focus should be on topics that will be of interest to upstream contributors. + +- Contributor/SIG blog posts +- Contributor events +- Process changes +- Release info, code freeze, et al +- Accomplishments (reaching 100,000 GitHub stars for example) +- Significant historical events as related to the project (Kubernetes birthday, previous events, etc.) +- Steering Committee Announcements +- Contributor guide/dev guide updates +- Work coming out of SIG-Contributor Experience + +Examples of topics that this group does NOT focus on include: + +- Content targeted at downstream users such as: + - Getting started with Kubernetes + - Best practices for running in production + +### Example Social Media + +- Weekly on Sunday: Link with community calendar and "This week in upstream community group meetings..." +- As they come in: + - Emails from k-dev + - #Shoutouts (from #shoutouts slack channel; try to include social handles or github handles if possible) + - Requests from issue templates +- Scheduled launches + - Your upcoming blog posts + - Requests from issue templates +- Every Wednesday (example) + - New contributor Wednesday - tweet a bunch of good-first-issue label GitHub issues (TODO: Automate) +- Event support: + - (with information from the issue template) + - Examples: Steering Committee voting will need a reminder weekly for at least a month + - Meet our contributors should have a reminder 3 days before the event and then 30 minutes before on the day of + +## KEPs + +([Kubernetes Enhancement Proposals]) + +### Ground Rules + +- The social media team cannot tweet KEPs at this time. +- This may change if we can get a few owner(s)/group who can approve them +- This guideline can only change with Steering, SIG-Arch, and SIG-Release approval + +### Frequently Asked Questions (FAQ) + +Q: Will the account follow other accounts? + +A: TODO (Y/N). The account is designed for information dissemination, so we will focus on that by (following no one and focusing on sharing || following everyone to extend our reach). + +Q: Do we engage with hostile messages? + +A: No. Don't feed the trolls. Mute them is the correct response. Block them as a last resort and only after discussing with team members. Reasons to block include verbal abuse, violating the platform's terms, or violating the [Code of Conduct](/code-of-conduct.md). The community is focused on openness and our accounts should be too, but there are times when we should reduce harmful people's visibility through blocking. + +Credit: [Fedora Community](https://fedoraproject.org/wiki/Marketing) + + +[#KEPs]: (#KEPs) +[Kubernetes Enhancement Proposals]: https://github.com/kubernetes/enhancements/tree/master/keps -- cgit v1.2.3 From 97f890c8bfc23ba618b29620522b3a672effd746 Mon Sep 17 00:00:00 2001 From: Matthew Broberg Date: Fri, 8 Oct 2021 10:17:13 -0500 Subject: Revise comms table --- communication/marketing-team/README.md | 6 ++++-- communication/marketing-team/role-handbooks/council.md | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/communication/marketing-team/README.md b/communication/marketing-team/README.md index 6094aaa2..76cd2a46 100644 --- a/communication/marketing-team/README.md +++ b/communication/marketing-team/README.md @@ -9,9 +9,11 @@ To better inform the Kubernetes contributor community and highlight their work t | Area & Handbook Link | Team | Notes | | --- | --- | --- | -| [Marketing Council] | program lead: @mbbroberg, program shadow: @JasonMorgan, promotion lead: @kaslin, liaison lead: @rajula96reddy | advisors: @parispittman, @chris-short. We always need more shadows! Reach out if interested. | +| [Marketing Council] Program Lead | @mbbroberg, shadow: @JasonMorgan,| advisors: @parispittman, @chris-short | +| [Marketing Council] Promotion Lead |@kaslin, shadow: `OPEN` | advisors: @parispittman, @chris-short. Shadow role is available. | +| [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 | New to Contributor Comms? Add your name here! -| Liaisons | release: @rajula96reddy, docs: `OPEN` | need support from Contributor Comms? Ping the liaison lead. ## Contact Us! diff --git a/communication/marketing-team/role-handbooks/council.md b/communication/marketing-team/role-handbooks/council.md index 9a2f1979..ea0e7b8e 100644 --- a/communication/marketing-team/role-handbooks/council.md +++ b/communication/marketing-team/role-handbooks/council.md @@ -6,7 +6,7 @@ The Marketing Council is made up of multiple individuals working to bring multip #### 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, Coucil members can cover multiple roles but with the intention of finding someone else to fill the position. Coverage is outlined in the [project README]. +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 -- cgit v1.2.3 From f728a4a13ba07bb924af92d5cd96fb1ab030e0d5 Mon Sep 17 00:00:00 2001 From: Matt Broberg Date: Fri, 12 Nov 2021 10:30:14 -0600 Subject: Update committee-steering/governance/sig-governance.md Co-authored-by: Stephen Augustus (he/him) --- committee-steering/governance/sig-governance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index b9dbadb0..7d19b26e 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -273,7 +273,7 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [The Release Team: Bug Triage, CI Signal, and more]: https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks [Production Readiness Reviewer]: https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#becoming-a-prod-readiness-reviewer-or-approver [API Reviewer and Moderator]: https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md#expanding-the-reviewer-and-approver-pool -[Marketing Council]: https://github.com/kubernetes/community/blob/master/communication/marketing-team/role-handbooks/council.md +[Marketing Council]: /communication/marketing-team/role-handbooks/council.md [Events Lead]: https://github.com/kubernetes/community/blob/master/events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ [monthly community meeting]: /events/community-meeting.md -- cgit v1.2.3 From bd05ffa78f0d835aaf5b9c2cd0565a3e6b4434ab Mon Sep 17 00:00:00 2001 From: Matthew Broberg Date: Fri, 12 Nov 2021 12:51:52 -0600 Subject: Links conform to org standards Signed-off-by: Matthew Broberg --- committee-steering/governance/sig-governance.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 7d19b26e..77510546 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -255,7 +255,7 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [lazy-consensus]: http://en.osswiki.info/concepts/lazy_consensus [super-majority]: https://en.wikipedia.org/wiki/Supermajority#Two-thirds_vote [KEP]: https://git.k8s.io/enhancements/keps/NNNN-kep-template/README.md -[sigs.yaml]: https://github.com/kubernetes/community/blob/master/sigs.yaml +[sigs.yaml]: /sigs.yaml [OWNERS]: contributors/devel/owners.md [SIG Charter process]: https://git.k8s.io/community/committee-steering/governance/README.md [Kubernetes Charter README]: https://git.k8s.io/community/committee-steering/governance/README.md @@ -271,10 +271,10 @@ Issues impacting multiple subprojects in the SIG should be resolved by either: [Google group]: https://groups.google.com/forum/#!forum/kubernetes-sig-config [dashboard]: https://testgrid.k8s.io/ [The Release Team: Bug Triage, CI Signal, and more]: https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks -[Production Readiness Reviewer]: https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#becoming-a-prod-readiness-reviewer-or-approver -[API Reviewer and Moderator]: https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md#expanding-the-reviewer-and-approver-pool +[Production Readiness Reviewer]: /sig-architecture/production-readiness.md#becoming-a-prod-readiness-reviewer-or-approver +[API Reviewer and Moderator]: /sig-architecture/api-review-process.md#expanding-the-reviewer-and-approver-pool [Marketing Council]: /communication/marketing-team/role-handbooks/council.md -[Events Lead]: https://github.com/kubernetes/community/blob/master/events/events-team/events-lead.md +[Events Lead]: /events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ [monthly community meeting]: /events/community-meeting.md [Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ -- cgit v1.2.3