Apache Way: Effective Open Source Project Management
summary
Explains concrete Apache project rules and practices: decision threads require at least 72-hour minimum for votes and formal votes record releases, all development must be archived on public mailing lists so the PMC and board can audit, core activity is conducted in English for oversight, contributions must use the Apache license and land in stages rather than one huge dump, and merit progresses from commit rights to PMC membership so communities stay diverse and long lived.
AI-written summary · about
chapters (26)
- 0:00The Apache Way Effective Open Source Project Management Shane Curcuru
- 0:31Apache Way: Introduction
- 1:41The Apache Way - Morning
- 3:36The Apache Way - Afternoon
- 5:16Apache Way Defining The Behaviors
- 5:50What we AREN'T Talking About
- 7:17Apache Way: Menu
- 8:51Decision Making - Consensus Preferred
- 10:10Decision Making - Votes When Needed
- 13:26Decision Making - Timeline
- 14:58Decision Making - No Deadlines
- 16:35Communication - Styles
- 17:30Communication - Conduct
- 19:22Communication - Language
- 24:18Community - No Jerks Allowed
- 26:24Community - Wear Your Hats
- 28:12Community - Check Affiliations At The Door
- 29:21Community - Independent Governance
- 32:20Open Development - Time Shifting
- 33:17Open Development - Archiving Everything
- 34:44Open Development - Transparent Decisions
- 37:08Open Development - Pragmatic License
- 40:26Merit - What YOU Can Do
- 41:53Merit - Growth
- 44:11Merit - Umbrella Projects Problem area: Umbrella projects
- 46:07The Apache Way Needs Your Input!
related talks
01h 00mGrow and manage your open source project with a proven way - The Apache Way
35mDecoding 'Community Over Code'
41mA user's perspective on open source
45mRunning an Apache Project: 10 Traps and How to Avoid Them
44mThe History of the Apache Software Foundation
22mKeynote: The Apache Way
35mOutreach: The Two-Way Street of Open Source Projects
38mHow To Be a Responsible Open Source Citizen