Improving a Large FOSS Project Sustainability
summary
LibreOffice updates strategy to close a funding gap: codebase is 7 million lines of code, user base ~100–200 million with 1M downloads/week, and development is currently 62% paid by ecosystem companies, ~30% volunteer and growing TDF-led development. Releases ship monthly with major versions every six months; a single shared engine runs desktop, mobile and cloud builds. Target: get large deployers to fund ~40% of seats (Italian MoD example) rather than remain unpaid takers, while resisting open‑core.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:05Office Suites Lifecycle
- 6:49LibreOffice Project Model
- 8:51LibreOffice Stakeholders
- 12:49Excerpts from Dries Buytaert (3)
- 18:15Relaunch the Innovation Visual Representation of the Fork
- 19:19Development Last 2 Years
- 20:40Who Pays LibreOffice Development?
- 21:38LibreOffice Technology
related talks
01h 00mLibreOffice: Improving the Project Sustainability
54mLibreOffice Technology, a FOSS platform for personal productivity
48mLibreOffice 10th Anniversary: the many faces of a global FOSS community
20mHow to make migrations to FOSS successful on the long term
01h 39mWorkshop: Building and Managing an Open Source Program Office
41mThis is bigger than us: Building a future for Open Source
44mThere's no sustainability problem in FOSS. Except that there is.
41mArchitecting for the Long Haul: Technical Strategies for Sustainable Open-Source Support Models