Maintaining a large OSS project: war stories
summary
Spree maintainer reports concrete changes and results: issue count jumps from 690 to about 2,630 after joining and February 2013 traffic spikes, commits go from 4,382 pre-join to ~4,016 afterward; the team renamed most files deliberately, extracts the authentication component ripped into a gem, replaces inconsistent JSON with a versioned API using ransack kaminari and ravel, adds currency configuration and multi‑currency pricing, introduces a checkout‑flow DSL, redesigns admin, and cuts bad releases by adopting TeamCity replacing Travis for CI.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:06boxfirepress "I'm having the same error and restarting heroku or resetting the database have not fixed the problem."
- 6:52boxfirepress "What part of same problem was difficult to understand?"
- 7:07Please don't expect help if you're going to be passive aggressive with
- 25:12SPREE DEVELOPER GUIDES
- 25:52Continuous Integration
related talks
16mMaintaining an OSS Project (Babel)
37mOpen Source Maintenance
21mThe OSS maintainer to staff engineer pipeline
23mScaling Open Source Communities
31mMaintaining a big open source project: lessons learned
39mMaintaining a big open source project: lessons learned
20mJuggling the dual life of an enterprise open source project
01h 28mBehind the OSS curtain: How we manage Spring
