The 7 biggest mistakes we made in 10 years of running a major open source project
summary
Project Lombok recounts concrete fixes: coping with 590 open issues by weekly triage and ruthless backlog cleanup; shipping edge/snapshot releases and a private Maven repo so users can test fixes; marking risky APIs in an experimental package to avoid breaking changes; adding an AUTHORS file to handle contributor licensing; using one million visitors metrics to justify ops readiness; tracking $100/month Patreon and six corporate licenses to show donations alone don’t fund maintenance.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:13What are we celebrating today
- 2:45Open issues
- 7:22Fixing bugs
- 11:32Art
- 11:57String
- 12:39ToString
- 23:00Experimental Features
- 24:52Mona Lisa
- 25:43Maintaining a website
- 29:09Pool Quests
- 32:00Bonus Lesson
- 32:50Authors File
- 33:25Introducing Contributors
- 38:13Finance
- 46:35Tightlift
related talks
34mThe 10 Biggest Mistakes You Shouldn’t Make In Open Source
31mMaintaining a big open source project: lessons learned
29mThe maintainability of open source code 20 years from today
39mA decade of lessons in Open Source licensing
49mOpen Source is Broken, and it’s Our Fault
45mFive ways open source will slow you down
10mMy Year In Open Source : 10 Lessons in 10 Minutes
14mWhat can we do to make Open Source more sustainable?