You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: communication/contributor-comms/role-handbooks/Social-Media.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
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.
6
6
7
-
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).
7
+
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).
8
8
9
9
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.
10
10
@@ -13,14 +13,14 @@ Do note that tweets targeting the greater Kubernetes community should potentiall
13
13
14
14
## Minimum Skills and Requirements
15
15
16
-
- Are a member of the [Kubernetes GitHub Org]
16
+
- Are a member of the Kubernetes GitHub Org
17
17
- Familiar with twitter by either having a personal account or managing another account (brand, oss project, employer, local nonprofit, etc)
18
-
- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channelnin the Kubernetes Slack
18
+
- Available to either attend regular Contributor Comms meetings or collaborate asynchronously via the #sig-contribex-comms channel in the Kubernetes Slack
19
19
20
20
### Expected Time Investment
21
21
22
22
Team leads: 3-5 hours per week.
23
-
Team members: 1-3 hour per week.
23
+
Team members: 1-3 hours per week.
24
24
25
25
## General Expectations
26
26
@@ -34,7 +34,7 @@ Team members: 1-3 hour per week.
34
34
35
35
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.
36
36
37
-
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.
37
+
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.
38
38
39
39
## Associates Overview (Shadow)
40
40
@@ -43,4 +43,4 @@ Leads should work with shadows to understand their capacity to take on the needs
43
43
* Becoming an owner (approver privileges) on the [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets) repo
44
44
* Watching for new tweet PRs and working with PR creators on scheduling/approving tweets
45
45
* Watching for new tweet requests and ensuring they get assigned to team members or created directly
46
-
* Taking on direct Twitter management
46
+
* Taking on direct management of a social media account
0 commit comments