Running an Apache Project: 10 Traps and How to Avoid Them
summary
Ten practical mistakes and how to fix them: start IP early so code grants and corporate sign‑offs don’t delay Apache entry; publish on apache.org and advertise to avoid duplicated projects; prefer reproducible builds and vote on source-only releases to avoid binary licensing nightmares; work openly and avoid no private forks or stealth development; loosen an exclusionary committer bar and measure code review to grow a diverse, multi‑employer community.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 5:23Mistake 1: Ignoring IP agreements
- 11:02Mistake 2: Keeping projects secret
- 15:19Mistake 3: Ignoring diversity
- 17:48Mistake 4: In-person decisions
- 22:06Mistake 5: Binary artifacts in releases
- 24:18Mistake 6: High committer bar
- 28:11Mistake 7: Trademark issues
- 32:05Mistake 8: Poor employee engagement
- 33:54Mistake 9: Stealth development
- 36:24Mistake 10: Licensing problems
- 39:55Summary and key takeaways
- 40:40Q&A: Getting started in Apache projects
related talks
01h 00mGrow and manage your open source project with a proven way - The Apache Way
47mThe Apache Way for Business
48mApache Way: Effective Open Source Project Management
38mHow To Be a Responsible Open Source Citizen
35mDecoding 'Community Over Code'
34mThe 10 Biggest Mistakes You Shouldn’t Make In Open Source
44mThe History of the Apache Software Foundation
41mA user's perspective on open source