Open communication for open development
summary
Starts with a concrete onboarding path: spend one hour a week reading a project’s community channels, follow mailing lists and issue trackers, answer recurring questions and get a first patch; observed conversion rates are 1 contributor per 100 users and 1 committer per 100 contributors; rely on archived mailing lists and linkable discussions for persistent context; plan to build an integrated internal search, handle permissions, run InnerSource training and learning paths, and treat planning, UX and metrics as visible artifacts to align contributors and managers.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 1:54Participating in open source
- 3:41Getting started with open source projects
- 6:30Benefits of public communication
- 8:19Building relationships remotely
- 10:47Turning contributors into committers
- 12:13Archiving conversations long term
- 14:24Safety in open communication
- 15:46Metrics and trust building
- 16:53Open source beyond engineering
related talks
42mBuilding On-Ramps for Non-Code Contributors in Open Source
15mThe Open Source Community Core
38mHow to bring open source to a closed community
13mOpen Web, Open Source, Open Communities
25mZero to Opensource Hero: A Journey to Enable a Culture Based on Open Source Contribu...
47mThe Great Adventure of Open Source Contribution
24mBuilding a Foundation for Open Collaboration
21mLeading and Growing an Open Source Comunity