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 <[email protected]>

Author: mbbroberg

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

communication/marketing-team/CHARTER.md

@@ -1,45 +1,39 @@
-# 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
 
 This team operates independently from Cloud Native Computing Foundation (CNCF) operations. The Team works with CNCF as needed but it exists within the Kubernetes governance model and is not a part or extension of CNCF Marketing. As such, this is not the team to reach out to about official CNCF Events and/or KubeCon. #kubecon on slack can be a helpful resource there. This team can assist in some ways with other CNCF projects but, the first priority of the team is Kubernetes.
 
 ## 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

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/

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