Skip to content

Commit d0fd6c1

Browse files
authored
Merge pull request #4620 from mrbobbytables/update-event-marketing-role
Update event marketing rolebook
2 parents 8c5f291 + ee096ea commit d0fd6c1

File tree

1 file changed

+58
-10
lines changed

1 file changed

+58
-10
lines changed
Lines changed: 58 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,24 @@
11
# Marketing Lead Handbook
22

3-
This document defines marketing planning and activities needed to run a Contributor Summit.
3+
This document defines marketing planning and activities needed to run a
4+
Contributor Summit.
45

56
- [Overview](#overview)
67
- [Skills and Qualifications](#skills-and-qualifications)
78
- [Responsibilities](#responsibilities)
9+
- [Communication Channels and Property Access](#communication-channels-and-property-access)
810
- [Documentation](#documentation)
911

1012
## Overview
1113

12-
As Marketing Lead, you are responsible for the overall marketing communications timeline. The role also includes ensuring all non-technical content (web, mail, physical prints) is correct and informative, and supporting the other roles (registration, content) as needed.
14+
As Marketing Lead, you are responsible for the overall marketing communications
15+
timeline. The role also includes ensuring all non-technical content (web, mail,
16+
physical prints) is correct and informative, and supporting the other roles
17+
(registration, content) as needed.
1318

14-
- Time Commitment
15-
- 1-3 hours a week from 0-1.5 months in
16-
- 2-5 hours a week from 1.5 months-to event
19+
Time Commitment:
20+
- 1-3 hours a week from 0-1.5 months in
21+
- 2-5 hours a week from 1.5 months-to event
1722

1823
## Skills and Qualifications
1924

@@ -26,16 +31,59 @@ As Marketing Lead, you are responsible for the overall marketing communications
2631
- Create a communication schedule - what, when, how, who
2732
- Manage online presence - website, social media strategy
2833
- Potentially recruit a social media coordinator role
29-
- Provide updates on social media, mailing lists, and Slack throughout pre-, during-, and post-event
30-
- Assist with GitHub event repo adds and edits
31-
- Work with Event Lead on a recap blog
34+
- Provide updates on social media, mailing lists, and Slack throughout pre-,
35+
during-, and post-event
36+
- Assist with GitHub event repo adds and edits
37+
- Work with Event Lead on a recap blog
3238
- Determine signage needs and copy, coordinate with CNCF on explicit needs
3339
- Create/update deck templates for curated talks and/or other purposes
3440

41+
### Communication Channels and Property Access
42+
43+
Communications to the Kubernetes Contributor Community should be sent from
44+
official Kubernetes accounts to ensure they reach the community. Mass messages
45+
from personal accounts can easily wind up being marked as spam.
46+
47+
**Email**
48+
49+
Mail should be sent from the [email protected] account. For access, work
50+
with the event lead who will coordinate with [SIG Contributor Experience leads]
51+
to grant temporary access to the account for the duration of the event.
52+
53+
**Twitter**
54+
55+
Tweets can be sent from two accounts: [@K8sContributors] and [@Kubernetesio].
56+
57+
Tweets targeting the greater Kubernetes community should use the [@Kubernetesio]
58+
account. Tweets using this account must be coordinated with the [CNCF]. Work
59+
with the CNCF events rep to schedule the tweets or put you in contact with
60+
the CNCF marketing members in charge of the account. Tweets using this account
61+
are often limited in the content and quantity that may be sent.
62+
63+
Tweets targeting the current contributor base should use the [@K8sContributors]
64+
account. There are no restrictions with this account for the amount or kind of
65+
messages that may be sent. This account may be used for announcements,
66+
live-tweeting, pictures and more. Reach out to the Kubernetes [upstream marketing
67+
team] to schedule or use this account.
68+
69+
3570
## Shadow to the Marketing Lead Role
36-
This role can include one or more shadows. The Marketing Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to lead one of the events-team roles in an upcoming summit. The shadows to the Marketing Lead are responsible for handling all Marketing lead related activities in the absence of the Lead.
71+
72+
This role can include one or more shadows. The Marketing Lead can delegate/assign
73+
tasks to the shadows. The expectation from a shadow is to lead one of the
74+
events-team roles in an upcoming summit. The shadows to the Marketing Lead are
75+
responsible for handling all Marketing lead related activities in the absence of
76+
the Lead.
3777

3878

3979
## Documentation
4080

41-
[Email comms used for Contributor Summit Barcelona, 2019](https://github.com/kubernetes/community/blob/master/events/2019/05-contributor-summit/communications.md)
81+
[Email comms used for Contributor Summit Barcelona, 2019]
82+
83+
84+
[Email comms used for Contributor Summit Barcelona, 2019]: /events/2019/05-contributor-summit/communications.md
85+
[SIG Contributor Experience leads]: /sig-contributor-experience/README.md#leadership
86+
[@K8sContributors]: https://twitter.com/K8sContributors
87+
[@Kubernetesio]: https://twitter.com/kubernetesio
88+
[CNCF]: https://www.cncf.io/
89+
[upstream marketing team]: /communication/marketing-team/README.md

0 commit comments

Comments
 (0)