Building an Open Source Community Beyond the Code
summary
Penpot positions community as the product’s growth engine: an 35-person core team coordinates transparent roadmaps and public feedback channels, the community produces 38 languages with paid West African translations to increase inclusion, and outreach targets four to five countries per continent plus offline meetups. Contribution pathways include nontechnical gestures (saying hi), design templates and visual docs, and a recent beta with ~100 volunteers → 16 active testers → 25+ insights implemented before release. A community-built desktop client proves feature gaps can be filled outside the core team.
AI-written summary · about
chapters (7)
- 0:00Introduction to Penpot
- 1:49Building inclusive open source
- 6:10Encouraging contributions
- 8:41Marketing open source tools
- 10:50Video and SEO strategies
- 12:35Community space and events
- 14:44Q&A on feedback and community contributions
related talks
29mDesigning Open Source - Building Communities
28mDesigning in the open: Mozilla Community Design
23mBuilding an open source design system for the many
16mOpen Source Design: Designing with the Community
31mMy Journey into Open Source Design
29mBuilding a culture of collaboration in OS communities with The Turing Way
23mThe most important component: community
22mOnboarding Designers into Open Source Projects