Skip to content

Latest commit

 

History

History
109 lines (67 loc) · 4.66 KB

README.md

File metadata and controls

109 lines (67 loc) · 4.66 KB
Raw

Kubernetes Release Team: Communications Coordinator

Overview:

The Communications Coordinator role is responsible for facilitating, empowering, and curating communication between the release team and various stakeholders including the Cloud Native Computing Foundation (CNCF), the media, contributing vendors, and Kubernetes project managers.

Additionally, there are specific deliverables that must come from the release process in the form of a release blog, event speaking opportunities, webinars, coordination of 5 Day blog series with the CNCF, and approved messaging for media. In the event that the release schedule slips, the communications coordinator will ensure press timing is synchronized and kept advised of the revised timing.

Requirements

Before continuing on to the Communications specific requirements listed below, please review and work through the tasks in the Release Team Onboarding Guide.

Skills and Experience Required:

  • Strong written and verbal communications skills
  • Experience with the Kubernetes release process enough to understand how communications milestones fit into the overall release
  • Existing relationships with the CNCF, relevant media personnel and outlets, Kubernetes project managers, and vendor stakeholders
  • A working knowledge of Kubernetes concepts
  • Project management experience is helpful

Expected Time Investment

The Kubernetes release cycle usually spans 12 weeks. The typical workload for the communications team is very light the first few weeks. In the later weeks of the release cycle, the workload can get very heavy.

The expected time investment for both leads and shadows are as follows:

  • 30 minutes to 2 hours a day, reviewing incoming KEPs and PRs, working with other SIGs or the CNCF on creating blog posts, and following Slack channels

  • 1 to 5 hours a week, attending Release Team (weekly) and Burndown meetings (daily during Code Freeze)

NOTE: These are estimates and your personal experience may vary. The more time you can spend working as a team and regularly communicating within your team, the better off your experience will be.

Slack Channel

There is a channel on the Kubernetes Slack workspace, release-comms, which is used by the communications release team to coordinate their efforts. If you're on the communications team, or applying to be, then it would be advantageous to follow along with the conversations.

Release Milestone Activities:

Week 1

  • Former communications coordinator helps identify new leads and shadows
  • Help finalize communications milestones in the release timeline
  • Look for event CFP deadlines to submit release to appropriate event; submit accordingly

Week 2

  • Begin organizing content from SIGs into blog topics, and high-level deliverables for the release
  • Begin attending release team meetings
  • Finalize lead and shadow roles

Week 3

  • Begin analyzing the release notes draft
  • Work with the enhancements lead to understand what might be delivered
  • Establish initial meeting with team to introduce everyone, collective tasks, and upcoming timelines

Week 4

  • Continue analysis of planned enhancements
  • Begin attending SIG meetings where enhancements will be delivered from

Week 5

  • Finalize release theme and messaging
  • Being working with the CNCF team to determine 5 blog series and schedule webinar

Week 6

  • Begin working with the CNCF communications team to schedule press and analyst pre-briefings and interviews
  • Work with the CNCF team to line up review blog post draft, discuss announcement timing and embargo release date, and discuss social posts

Week 7

No activities scheduled

Week 8

No activities scheduled

Week 9

  • Begin attending burndown meetings
  • Start weekly meeting with the CNCF marketing team
  • Work with the CNCF communications team to schedule press and analyst pre-briefings and interviews; provide team draft blog to send to media under embargo
  • Begin organizing media roundtable event (if appropriate)

Week 10

  • Begin finalizing the blog
  • Schedule social updates
  • Work with the CNCF communications team to continue to schedule press and analyst pre-briefings and interviews

Week 11

  • Finalize the blog, and adjust based on what was delivered
  • Coordinate release timing with the CNCF, Media, Release team (not embargo for media stories may release this week)

Week 12

  • Release day
  • Continue managing release timing in case of delay
  • Publish the blog
  • Help identify release team and community members for media interview requests

Week 13

  • Release retrospective participation
  • Follow-up support with the media
  • Obtain media coverage report from the CNCF team