Merge pull request #3854 from jonasrosland/update-events
Add more Contributor Summit marketing lead info and cleanup of best practices
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
b702af9225
|
|
@ -1,3 +1,5 @@
|
||||||
|
# Best pracices for running a Kubernetes Contributor Summit
|
||||||
|
|
||||||
New home for best practices, process documentation, and other artifacts that detail out the 'how to' of running a Kubernetes contributor summit.
|
New home for best practices, process documentation, and other artifacts that detail out the 'how to' of running a Kubernetes contributor summit.
|
||||||
|
|
||||||
//TODO
|
//TODO
|
||||||
|
|
@ -5,7 +7,23 @@ general clean up; style guide check
|
||||||
add more reference links
|
add more reference links
|
||||||
potentially separate into multiple docs or re-organize
|
potentially separate into multiple docs or re-organize
|
||||||
|
|
||||||
## Kick Off
|
- [Kickoff](#kickoff)
|
||||||
|
- [Project Management](#project-management)
|
||||||
|
- [Registration](#registration)
|
||||||
|
- [Badges](#badges)
|
||||||
|
- [Venue](#venue)
|
||||||
|
- [Social / Celebration](#social-celebration)
|
||||||
|
- [Communication and Advertising](#communication-and-advertising)
|
||||||
|
- [Sponsorship](#sponsorship)
|
||||||
|
- [Swag / T-Shirts](#swag-t-shirts)
|
||||||
|
- [Day of Event Staff](#day-off-event-staff)
|
||||||
|
- [Transparency](#transparency)
|
||||||
|
- [Signage](#signage)
|
||||||
|
- [Contributor Awards](#contributor-awards)
|
||||||
|
- [Survey](#survey)
|
||||||
|
- [Resources](#resources)
|
||||||
|
|
||||||
|
## Kickoff
|
||||||
Event lead will start the event strategy doc that will outline goals and content
|
Event lead will start the event strategy doc that will outline goals and content
|
||||||
strategy with content team. This doc should first be circulated within contributor experience for
|
strategy with content team. This doc should first be circulated within contributor experience for
|
||||||
the [event OWNERs] to review and for the SIG to weigh in. Next, steering committee
|
the [event OWNERs] to review and for the SIG to weigh in. Next, steering committee
|
||||||
|
|
@ -14,10 +32,10 @@ content for most of different types of contributors that we have.
|
||||||
|
|
||||||
[Seattle 2018 doc]
|
[Seattle 2018 doc]
|
||||||
|
|
||||||
A GitHub page in the events section will be created to capture history, the team, and other basic information. [(example)] This will not be used as the event website.
|
A GitHub repo in the events section will be created to capture history, the team, and other basic information. [(example)] This will not be used as the event website.
|
||||||
|
|
||||||
## Project Management
|
## Project Management
|
||||||
Each event will have a [project board] created. The incoming team will need to create a label `area/cityfoo-summit` and any issue or PR related to all summits will have the label `area/contributor-summit`.
|
Each event will have a [project board] created. The incoming team will need to create a label `area/regionfoo-summit` and any issue or PR related to all summits will have the label `area/contributor-summit`.
|
||||||
|
|
||||||
The event team can decide if they want a dedicated project manager role at the time of planning.
|
The event team can decide if they want a dedicated project manager role at the time of planning.
|
||||||
|
|
||||||
|
|
@ -40,17 +58,17 @@ Accessibility
|
||||||
|
|
||||||
If the event is being held during KubeCon/CloudNativeCon it's important to get a space that is not with other co-located events to avoid confusion like we have had in the past.
|
If the event is being held during KubeCon/CloudNativeCon it's important to get a space that is not with other co-located events to avoid confusion like we have had in the past.
|
||||||
|
|
||||||
## Social
|
## Social / Celebration
|
||||||
Hallway Track is listed as the favorite track at every event. The social is a longer hallway track that doesn't interfere with content. The social should have fun activities!
|
The Hallway Track is listed as the favorite track at every event. The social/celebration is a longer hallway track that doesn't interfere with content. The social should have fun activities!
|
||||||
|
|
||||||
## Communication and Advertising
|
## Communication and Advertising
|
||||||
kubernetes-dev@googlegroups.com is our artery for contributor communication and should be the main news network for contributor events.
|
[kubernetes-dev@googlegroups.com][k-dev] is our artery for contributor communication and should be the main news network for contributor events.
|
||||||
Other channels:
|
Other channels:
|
||||||
Slack - #contributor-summit, #kubecon, #kubernetes-dev
|
Slack - [#contributor-summit], [#kubecon], [#kubernetes-dev]
|
||||||
Twitter
|
[Twitter]
|
||||||
Kubernetes blog
|
[Kubernetes blog]
|
||||||
discuss.kubernetes.io
|
[discuss.kubernetes.io]
|
||||||
Thursday Community Meetings
|
[Weekly Thursday Community Meetings][community-meetings]
|
||||||
|
|
||||||
## Sponsorship
|
## Sponsorship
|
||||||
We like to keep our events clear from sponsorships as it distracts from the mission.
|
We like to keep our events clear from sponsorships as it distracts from the mission.
|
||||||
|
|
@ -58,8 +76,9 @@ We like to keep our events clear from sponsorships as it distracts from the miss
|
||||||
## Swag / T-Shirts
|
## Swag / T-Shirts
|
||||||
What messaging do we want to convey with the swag?
|
What messaging do we want to convey with the swag?
|
||||||
thockin has designed all contributor summit NA shirts and jberkus for Shanghai; both have done an EU shirt
|
thockin has designed all contributor summit NA shirts and jberkus for Shanghai; both have done an EU shirt
|
||||||
|
|
||||||
Best practices:
|
Best practices:
|
||||||
Order shirts 10 days before the event to make sure everyone gets the size that they want unless there are custom/shipping issues.
|
Order shirts well in advance before the event to make sure everyone gets the size that they want in case there are custom/shipping issues.
|
||||||
Past brand that works well: Dakota. Previous brands had odd sizing and community feedback matched that.
|
Past brand that works well: Dakota. Previous brands had odd sizing and community feedback matched that.
|
||||||
|
|
||||||
## Day of Event Staff
|
## Day of Event Staff
|
||||||
|
|
@ -98,3 +117,11 @@ Links to docs that aren't a fit for markdown:
|
||||||
[blog post example]: https://kubernetes.io/blog/2018/10/16/kubernetes-2018-north-american-contributor-summit/
|
[blog post example]: https://kubernetes.io/blog/2018/10/16/kubernetes-2018-north-american-contributor-summit/
|
||||||
[welcome slides]: https://docs.google.com/presentation/d/11eDR_0Dl_MBbeoMDF_mQaJC3shnnd6buhIVei2Ke0SM/edit#slide=id.p
|
[welcome slides]: https://docs.google.com/presentation/d/11eDR_0Dl_MBbeoMDF_mQaJC3shnnd6buhIVei2Ke0SM/edit#slide=id.p
|
||||||
[project board]: https://github.com/orgs/kubernetes/projects
|
[project board]: https://github.com/orgs/kubernetes/projects
|
||||||
|
[k-dev]: (https://groups.google.com/forum/#!forum/kubernetes-dev)
|
||||||
|
[#contributor-summit]: (https://kubernetes.slack.com/messages/contributor-summit)
|
||||||
|
[#kubecon]: (https://kubernetes.slack.com/messages/kubecon)
|
||||||
|
[#kubernetes-dev]: (https://kubernetes.slack.com/messages/kubernetes-dev)
|
||||||
|
[Twitter]: (https://twitter.com/kubernetesio)
|
||||||
|
[Kubernetes blog]: (https://kubernetes.io/blog/)
|
||||||
|
[discuss.kubernetes.io]: (discuss.kubernetes.io)
|
||||||
|
[community-meetings]: (https://github.com/kubernetes/community/blob/master/events/community-meeting.md)
|
||||||
|
|
|
||||||
|
|
@ -1,29 +1,39 @@
|
||||||
Marketing Lead Handbook
|
# Marketing Lead Handbook
|
||||||
(and supplemental marketing documentation needed to run a Contributor Summit)
|
|
||||||
|
This document defines marketing planning and activities needed to run a Contributor Summit.
|
||||||
|
|
||||||
|
- [Overview](#overview)
|
||||||
|
- [Skills and Qualifications](#skills-and-qualifications)
|
||||||
|
- [Responsibilities](#responsibilities)
|
||||||
|
- [Documentation](#documentation)
|
||||||
|
|
||||||
## Overview
|
## Overview
|
||||||
|
|
||||||
TODO
|
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.
|
||||||
|
|
||||||
|
- Time Commitment
|
||||||
|
- 1-3 hours a week from 0-1.5 months in
|
||||||
|
- 2-5 hours a week from 1.5 months-to event
|
||||||
|
|
||||||
## Skills and Qualifications
|
## Skills and Qualifications
|
||||||
|
|
||||||
TODO
|
- Good grasp on general marketing activities surrounding events
|
||||||
|
- Understanding of common forms of marketing communications
|
||||||
|
- Event planning experience
|
||||||
|
|
||||||
## Activities
|
## Responsibilities
|
||||||
|
|
||||||
Create a communication schedule - what, when, how, who
|
- Create a communication schedule - what, when, how, who
|
||||||
Figure out online presence - website, social media strategy
|
- Manage online presence - website, social media strategy
|
||||||
Potentially recruit a social media coordinator role
|
- Potentially recruit a social media coordinator role
|
||||||
Provide social updates throughout pre-during-and post event
|
- Provide updates on social media, mailing lists, and Slack throughout pre-, during-, and post-event
|
||||||
Assist with GitHub page
|
- Assist with GitHub event repo adds and edits
|
||||||
Work with lead on a recap for blog
|
- Work with Event Lead on a recap blog
|
||||||
Determine signage needs and copy, coordinate with cncf on explicit needs
|
- Determine signage needs and copy, coordinate with CNCF on explicit needs
|
||||||
Create a deck template for curated talks and/or other purposes
|
- Create/update deck templates for curated talks and/or other purposes
|
||||||
|
|
||||||
## Time Commitment
|
|
||||||
1-3 hours a week from 0-1.5 months in
|
|
||||||
2-5 hours a week from 1.5 months-to event
|
|
||||||
|
|
||||||
## Misc Info, Docs to link, etc.
|
|
||||||
|
|
||||||
TODO
|
## Documentation
|
||||||
|
|
||||||
|
[Email comms used for Contributor Summit Barcelona, 2019](https://github.com/kubernetes/community/blob/master/events/2019/05-contributor-summit/communications.md)
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue