diff --git a/committee-steering/governance/sig-governance.md b/committee-steering/governance/sig-governance.md index 5a675476a..6589b113d 100644 --- a/committee-steering/governance/sig-governance.md +++ b/committee-steering/governance/sig-governance.md @@ -184,7 +184,7 @@ Example of SIG roles created to help operations: - [Production Readiness Reviewer] - [Events Lead] - [PR Wrangler] -- [Marketing Council] +- [Contributor Comms] Other roles... - *MUST* be tracked on the SIGs README with a link to the role definition. @@ -258,7 +258,7 @@ otherwise fulfill its Organizational Management responsibilities [The Release Team: Bug Triage, CI Signal, and more]: https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks [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 +[Contributor Comms]: https://github.com/kubernetes/community/tree/master/communication/contributor-comms/role-handbooks [Events Lead]: /events/events-team/events-lead.md [PR Wrangler]: https://kubernetes.io/docs/contribute/participate/pr-wranglers/ [Inclusive Open Source Community Orientation course]: https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/ diff --git a/communication/calendar-guidelines.md b/communication/calendar-guidelines.md index 3446fc772..a07de28fa 100644 --- a/communication/calendar-guidelines.md +++ b/communication/calendar-guidelines.md @@ -140,9 +140,9 @@ Google group: #### Example -> SIG-Contribex: Weekly Marketing Meeting +> SIG-Contribex: Weekly Contributor Comms Meeting > -> https://github.com/kubernetes/community/tree/master/communication/marketing-team +> https://github.com/kubernetes/community/tree/master/communication/contributor-comms > > **Time**: Weekly on Friday from 8-9am PT > diff --git a/communication/contributor-comms/storytelling-resources/event-checklist.md b/communication/contributor-comms/storytelling-resources/event-checklist.md index 48549da41..d0aad5f2c 100644 --- a/communication/contributor-comms/storytelling-resources/event-checklist.md +++ b/communication/contributor-comms/storytelling-resources/event-checklist.md @@ -1,4 +1,4 @@ -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. +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 [contributor-comms README](../README.md) for info on the team. # Pre-Event (KubeCon) Checklist diff --git a/communication/contributor-comms/storytelling-resources/multichannel-communications.md b/communication/contributor-comms/storytelling-resources/multichannel-communications.md index dd0b786fb..1e1e35c01 100644 --- a/communication/contributor-comms/storytelling-resources/multichannel-communications.md +++ b/communication/contributor-comms/storytelling-resources/multichannel-communications.md @@ -84,4 +84,4 @@ To find SIG-specific channels, check the Contact column in the [SIG list](https: ## Questions? -Have a question about what's written here or something else? Reach out to the [marketing team](README.md)! +Have a question about what's written here or something else? Reach out to the [contributor-comms](../README.md)! diff --git a/events/events-team/marketing/README.md b/events/events-team/marketing/README.md index f6520b7fe..5dc2d8ff4 100644 --- a/events/events-team/marketing/README.md +++ b/events/events-team/marketing/README.md @@ -63,8 +63,7 @@ are often limited in the content and quantity that may be sent. Tweets targeting the current contributor base should use the [@K8sContributors] account. There are no restrictions with this account for the amount or kind of messages that may be sent. This account may be used for announcements, -live-tweeting, pictures and more. Reach out to the Kubernetes [upstream marketing -team] to schedule or use this account. +live-tweeting, pictures and more. Reach out to the Kubernetes [Contributor Comms] to schedule or use this account. ## Shadow to the Marketing Lead Role @@ -86,4 +85,4 @@ the Lead. [@K8sContributors]: https://twitter.com/K8sContributors [@Kubernetesio]: https://twitter.com/kubernetesio [CNCF]: https://www.cncf.io/ -[upstream marketing team]: /communication/marketing-team/README.md +[SIG-ContribEx Contributor Comms team]: /communication/contributor-comms/README.md diff --git a/mentoring/programs/shadow-roles.md b/mentoring/programs/shadow-roles.md index 9ba31e7f7..44ea6011d 100644 --- a/mentoring/programs/shadow-roles.md +++ b/mentoring/programs/shadow-roles.md @@ -28,13 +28,13 @@ Production readiness reviews are intended to ensure that features merging into K The list of roles and duties can be found [here](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md) -## Upstream Marketing -The mission of the Kubernetes Upstream Marketing Team is to elevate the hard work being done throughout the Kubernetes +## Contributor Comms +The mission of the Kubernetes Contributor Comms 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 +force behind the Kubernetes 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. -The list of roles and duties can be found [here](https://github.com/kubernetes/community/blob/master/communication/marketing-team/CHARTER.md) +The list of roles and duties can be found [here](https://github.com/kubernetes/community/tree/master/communication/contributor-comms/role-handbooks) ## SIG-Docs-Blog The Kubernetes Blog Subproject is owned by SIG-Docs and run by the Editorial Team.