Pragmatic Community Driven Development in Ruby
summary
Case study of building ruport the Ruby reporting library: why the project switches license to match Ruby to avoid friction, why it moves issue tracking from mailman to Track and mirrors with svk to RubyForge, how a small mailing list and a simple roadmap cut 15 months of scope drift, how a plug‑in system removes work-from-work code, and concrete outcomes — regular releases with a production target May 15 and roughly 8–10 patches/month after the tooling and docs improve.
AI-written summary · about
