Comms & Social Media - Why Does a Project Need It
Talkat CNCF Maintainer Summit Europe 2025 · on Monday, 2025-03-31· at 15:20· Level 3 | ICC Capital Suite 10-12·
summary
Project comms explains why a formal communications function is essential once a project reaches scale, showing concrete wins and failures: the deprecate docker shim episode spawns thousands of posts and forces coordinated vendor outreach, automated alerts, and FAQs; tools used include Buffer and Sepia for automated social posting and DNS verification for Blue Sky accounts; channels are chosen by audience and creator presence rather than aspirational coverage; result: reclaimed accounts, a contributor comms team, and rapid cross‑vendor notifications that prevent cluster breakage and lower user impact.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:04Kubernetes comms evolution
- 3:12Why projects need comms
- 6:46Docker shim deprecation lessons
- 9:17Audience perceptions and mental models
- 11:23Learning and communication changes
- 12:27Targeting contributor and user groups
- 13:52Choosing social media channels
- 16:44Content types and platform fit
- 18:48Resource allocation for channels
- 20:31Automating comms and tools
- 21:15Growth metrics and performance
- 22:40Content planning challenges
- 23:42Onboarding contributors via comms
- 25:07Coordinating vendor communications
- 26:32Social media policies
- 28:41CNCF comms resources
- 29:24Q&A
related talks
34mCommunication Strategy for OS Projects: Get Engineers to Think About Comms Channels
32mReviving Comms Through Communication
44mPanel Discussion: Finding the Right Comms for Your Community...
28mBuilding Better Communication for Kubernetes Contributors with Marketing
28mBuilding Culture through Communication
49mCommunities Over Code: How to Build a Successful Project
59mGoing Rogue: How Community & Connections Can Stealth Market Your Projects
35mCommunication is a Technical Skill