Humans of Open Source
summary
Stories of projects like webdriverio and appium show code becomes community only when maintainers document context, groom issues and lower onboarding pain by splitting scope and packages; concrete tactics include choosing accessible tech (beware TypeScript or Mac‑only builds), writing contribution guidelines, flagging “good first” issues, offering office hours via Calendly, granting org access to active contributors, and planning for burnout and governance through foundations such as OpenJS Foundation or Software Freedom Conservancy.
AI-written summary · about
chapters (5)
related talks
13mOpen Web, Open Source, Open Communities
42mBuilding On-Ramps for Non-Code Contributors in Open Source
33mIncluding People
36mThe Feedback Loop: Growing healthy open source projects
20mOpen up to Open Source
23mKeeping Your Open Source Project Accessible to All
10mKeynote: How to Become an Open Source Mechanic
38mThe Unbearable Vulnerability of Open Source
