Building Developer Community One Pull Request at a Time
summary
Maintains more than 10 GitHub repos (one hits 100+ commits per week) and runs internal State Based Logging pipelines; prescribes a clear vision, a core team that signs off on critical areas, and automation plus lightweight process that prevents stalled PRs. Uses a design-first PRs flow (design issue approved before code), public sprint milestones, occasional conference calls, a single rotating reviewer to clear community backlog, and explicit contributor credit to turn students and external users into repeat contributors (one reviewer owner, public sprint milestones).
AI-written summary · about
chapters (14)
- 0:00Start
- 1:01Intro
- 3:08Plant Metaphor: What it takes to Grow One
- 4:43Vision and Principles
- 6:08You Need a Good Core
- 8:21Ownership and Responsibility
- 11:25community without strong
- 13:59Transparent Planning
- 17:20Use Design Reviews to Avold Surprises at Pull Request Time
- 21:29React To Questions and Pull Requests Immediately
- 23:21Show Empathy and Backbone
- 27:23Make your Project Someone's Learning Opportunity
- 28:57Project with good foundation and process but without human support
- 29:39Putting it All Together
related talks
39mCommunity and Contributors Panel
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
43mMy First Year of Pull Requests
27mManaging A Healthy GitHub Community
15mBuilding The Open Source Community We Want
51mBuilding Strong and Sustainable Open Source Projects
22mYour Open Source Repo Needs A Project Manager
25mHow to Grow and Mentor an Open Source Community & Achieve Collaboration with Over 170...