Open Source Community Building
summary
An open source collective reports three developers, five apps and about a thousand community members, resurrecting three abandoned apps; a 1,000-project study finds 93% male contributors, >50% paid contributors, >35% in Europe and <15% in Asia/Pacific. Recommended practices: use Matrix and Telegram for outreach, add anonymized channels and translations, apply human‑centered design cycles for privacy UX and developer guidelines, organise a community council for mediation, and accept forking as the final conflict resolution.
AI-written summary · about
chapters (20)
- 0:00Open source community building
- 1:59Speakers' backgrounds
- 5:28What is FOSS
- 7:15Motivations to contribute
- 8:19FOSS community challenges
- 10:03Governance models
- 12:10Conflict resolution
- 15:20Single-dev dynamics
- 17:10Engaging non-tech contributors
- 18:36Human-centric FOSS design
- 24:07Letting contributors lead
- 25:55Dark side of FOSS
- 26:17Geopolitical exclusion
- 28:26Sexism in FOSS
- 30:18Inclusive governance
- 31:47Non-code contributors
- 32:51Community governance discussion
- 33:56Q&A
- 37:31Encouraging participation
- 39:17Closing remarks
related talks
35mBuilding an Open Source Community to Achieve Innovation-Through-Openness - Jonas Rosland
18mOpen communication for open development
28mBuilding Open Source Communities
49mCommunities Over Code: How to Build a Successful Project
27mOpen Source: Supporting, Contributing and Evangelising
52mBottom-Up Open Source Culture
25mThis is bigger than us: Building a future for Open Source
41mThis is bigger than us: Building a future for Open Source