The maintainability of open source code 20 years from today
summary
A practical postmortem of Lucene/Solr maintenance with concrete wins and pain points: history of the 2010 merge and recent split, a documented pull request that removed oppressive language and who backported it, addition of CI badges around 2019 and ongoing flaky-test work, benchmarks showing analyzer performance deltas over time, security hardening (security manager changes and incident responses), and active feature work like approximate nearest vector search in main plus a reference implementation aimed at scaling and testing.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:34Doug Cutting
- 3:20Doug's Search Lineage
- 8:10Apache Lucene
- 9:10Maintenance
- 10:57Code Clarity
- 12:23Project Awareness
- 13:51Project Health
- 14:22Improvement
- 15:32Don't Alert Security Team
- 17:22Vector Search
- 18:26The Next Big Thing
related talks
31mHow to contribute to the community & become an OpenSearch Maintainer
37mOSS Security: Lessons from 10+ Years at Apache Solr
19mRoad To Maintainership: Shaping OpenSearch's Future
25mThe Maintainer’s Perfect Storm: Survival, Succession, and a Decoupled Future
50mThe 7 biggest mistakes we made in 10 years of running a major open source project
36mState of Open Source in 2024
35mTending Your Open Source Garden
47mProject Talk: Maintenance Update