Get yourself heard in Open Source
summary
Concrete playbook for getting code and people moving: how refactor the Bartik theme starts as a few tiny issues, scales into a maintainer role, and produces dozens of novice contributions; how triage the issue queue and pairing at sprints or hangouts speeds issues to review and RTBC; how outreach — asked for help on Twitter — and mentoring bring unexpected volunteers; warnings about burnout and communication pitfalls and specific asks (tests, theme system work, 8.1 bug fixes) show real, actionable next steps.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:24About Emma
- 1:18Frontend
- 2:43Why Drupal
- 3:18For the people
- 3:46After Drupalcamp
- 4:30Focus on Frontend
- 4:48Learn Frontend
- 6:40Read
- 7:50Shadow someone
- 8:51Issue queues
- 10:46Learn twig
- 11:51Open your mouth
- 12:55Liftoff
- 13:07Start really small
- 14:01Tell people what to do
- 14:49Open as possible
- 15:16Ask for help
- 16:08Call for support
- 16:42Faith in humanity
- 16:58Mentoring sprints
- 17:21Obstacles
- 17:47Interpreting communication
- 19:40Taking on too much
- 21:32Help us
- 26:43Thank you
related talks
47mThe Great Adventure of Open Source Contribution
20mOpen up to Open Source
42mBuilding On-Ramps for Non-Code Contributors in Open Source
16mThe Open Source Community Playbook: What Works, What Doesn’t, and Why
24mSo You Want to Contribute to Open Source: ...
44mBuilding On-Ramps for Non-Code Contributors in Open Source
27m"Getting Started with Open Source Contributions"
15mMaking Meaningful Contributions to Open Source Contributions