Communication Strategy for OS Projects: Get Engineers to Think About Comms Channels
summary
Maps every channel to an outcome using a communications logic model adapted for open source: channels → artifacts → short/mid/long outcomes. Applied a logic model to Apache Beam to find redundancies (two blog platforms) and gaps (too few contributor workshops), then proposes three concrete moves: concentrate the blog on the main site, add recorded and live workshops, and boost tech‑talk distribution. The model becomes a one‑page table for contributors, lands on the Apache Beam wiki, informs a website redesign, and yields consensus to implement the changes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:45Working in Public
- 1:40Online Collaboration
- 3:00Communication Channels
- 3:28The Problem
- 4:04The Logic Model
- 5:40Apache Beam Example
- 11:28Apache Beam Logic Framework
- 17:10Outcomes
- 18:25Questions
- 21:23Logic Model Approach
- 22:48Wikimedia Foundation
- 26:36Social Media Policy
- 28:13Chat Rooms
related talks
37mComms & Social Media - Why Does a Project Need It
24mBuilding a Foundation for Open Collaboration
17mScaling Community, Code, Contributors
28mBuilding Open Source Communities
20mThe Good, The Bad, and The Data: Marketing Strategies
29mBeing Successful at Open Source
15mHow to achieve effective Open source collaboration
25mNavigating the Waters: Balancing Open Source Activities in Corporate Environments