Lessons Learned in Building an Interdependent Open Source Team
summary
Open source team design for Alluxio focuses on measurable work: a three‑function split (Community, DevRel, OSS/R&D), concrete metrics (GitHub + community activity as constant KPIs), and staged programs (a seven‑stage user journey and four user types). Team started with two hires end of 2019 and scales via partnerships and content — published Trino and Presto optimization handbooks, built collaborations like RaptorX with Meta, recruited Presto committers, and supports 10,000 Slack members and ~1,200 GitHub contributors with a 24‑hour response target for DevRel.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:41Agenda
- 1:09Rough Agenda
- 1:38About Luxio
- 2:42Who do we serve
- 3:29Who are our users
- 4:22How we structure our team
- 5:42Awareness Adoption
- 6:22Open Source Community
- 8:55User Representation
- 11:50Team Explained
- 17:17What Does Your Team Covers
- 20:26Draw People From Different Teams
- 20:38Define User Types
- 21:47User Journey
- 23:01Flywheel
- 23:44Super Contributors
- 25:24Examples
- 25:42Building Blocks
- 26:59Community Collaboration
- 29:35SAS Founding Napkin
- 31:47SAS User Journey
- 32:29Community Survey
- 37:21Questions
- 38:20Community Team
related talks
38mBuilding Super-Contributors in Alluxio Open Source Community
51mLessons from Joining a Large Open Source Project
20mBuilding a Team for the Upstream: Things We Learned Building InnerSource Teams for Open Source Impact
48mLessons Learned from Open Source in Business
24mBuilding a Foundation for Open Collaboration
39mExtrospective OSPOs: Working on 3rd Party OSS
29mDesigning Open Source - Building Communities
35mBuilding an Open Source Community to Achieve Innovation-Through-Openness - Jonas Rosland