diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2023-02-04 16:58:29 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-04 16:58:29 -0800 |
| commit | 5d0f5180d1dea5212ae45d154de9a8ffdeeee6dc (patch) | |
| tree | 854b1bb712f6bc24f0996a9687a631d518489be2 /communication | |
| parent | 1e73448d837497126a3891e662ea04ce8c7b62a6 (diff) | |
| parent | 51279eb7bb40ed23efeb3740b89ea6a399e4abef (diff) | |
Merge pull request #7089 from SD-13/fix_typo_1
FIX: Typos in Comms social media role-handbook
Diffstat (limited to 'communication')
| -rw-r--r-- | communication/contributor-comms/role-handbooks/Social-Media.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/communication/contributor-comms/role-handbooks/Social-Media.md b/communication/contributor-comms/role-handbooks/Social-Media.md index f1a1b36b..972a545e 100644 --- a/communication/contributor-comms/role-handbooks/Social-Media.md +++ b/communication/contributor-comms/role-handbooks/Social-Media.md @@ -4,7 +4,7 @@ This handbook outlines expectations and responsibilities for Social Media Leads as well as Contributor Comms team members who wish to contribute to social media efforts. -Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At time of writing, the primary social media channel we communicate through is the [@K8sContributors handle on twitter](https://twitter.com/K8sContributors). +Social Media leads' contributions further the Contributor Comms team's efforts to communicate with contributors on a broad scale through social media. At the time of writing, the primary social media channel we communicate through is the [@K8sContributors handle on twitter](https://twitter.com/K8sContributors). Any Kubernetes contributor can write tweets to be distributed through the twitter handle by utilizing the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets). This repo utilizes the open source [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweeting approved from the @K8sContributor handle. The repo also features automation to convert issues into PRs, to make it easier to create tweets with minimal interaction with Github's PR process. @@ -13,14 +13,14 @@ Do note that tweets targeting the greater Kubernetes community should potentiall ## Minimum Skills and Requirements -- Are a member of the [Kubernetes GitHub Org] +- 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) -- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channelnin the Kubernetes Slack +- 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: 3-5 hours per week. -Team members: 1-3 hour per week. +Team members: 1-3 hours per week. ## General Expectations @@ -34,7 +34,7 @@ Team members: 1-3 hour per week. The leader(s) of the social media team will be expected to monitor the @K8sContributors handle. Retweets, replies, and responding to replies appropriately fall under the purview of the social media lead. Time-sensitive tweets should also be handled directly by the team lead. Team leads should coordinate with team members to plan tweets in advance, particularly for large contributor-focused events such as KubeCon or Contributor Summit. -Team members will be expected to keep an eye out for news in need of tweeting. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack. Team members can submit less time-sensitive tweets to the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) for review and tweeting. +Team members will be expected to keep an eye out for news in need of tweeting. Common sources of such announcements are the k-dev mailing list and the #sig-contribex-comms channel on Slack. Team members can submit less time-sensitive tweets to the [kubernetes-sigs/contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) for review and tweeting. ## Associates Overview (Shadow) @@ -43,4 +43,4 @@ Leads should work with shadows to understand their capacity to take on the needs * Becoming an owner (approver privileges) on the [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) repo * Watching for new tweet PRs and working with PR creators on scheduling/approving tweets * Watching for new tweet requests and ensuring they get assigned to team members or created directly -* Taking on direct Twitter management +* Taking on direct management of a social media account |
