Committed to The Apache Way
summary
Argues that being a committer is about measurable project value not a job title, cites joining in 2008, watching project lists for six to eight months before posting, and first meeting the community in person in 2014. Says non‑coding work — documentation, testing, marketing, community management — earns merit not title, and the public mailing list is crucial: mailing list is the front door watched by potential contributors. Recommends recruit from user lists, focus disputes on the project’s welfare, and build caretakers for long‑term survival.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:07Agenda
- 1:47Definitions
- 2:49Committer
- 4:20Code
- 7:25Noncoding contributions
- 10:22Sharans background
- 12:55The ASF
- 15:47Project Management Committee
- 17:05Project Planning
- 18:14What did you do
- 20:40Who have invisible friends
- 23:18The common room
- 27:31Escape attempts
- 31:17Treatment plan
- 34:56Symptom
- 36:40Summary
related talks
01h 00mGrow and manage your open source project with a proven way - The Apache Way
35mDecoding 'Community Over Code'
34mBeing Your Best Asset and Not Your Worst Enemy
41mA user's perspective on open source
18mOpen communication for open development
31mNon-Code contributions (...)
34mHow to get them to Commit?
24mSo You Want to Contribute to Open Source: ...