From OpenOffice.org to LibreOffice: Forking a Major Productivity Suite
Sun's release of StarOffice source created OpenOffice.org, and the later LibreOffice fork showed how a community can preserve and redirect a major open-source codebase when governance priorities diverge.
The problem that created the project
Sun Microsystems acquired Star Division and its StarOffice suite in 1999, then released much of the code as OpenOffice.org in 2000. Apache OpenOffice’s history records this lineage from proprietary office software into a large public codebase. [1] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
A proprietary codebase opens
Releasing StarOffice code brought open collaboration into a difficult office-productivity category with complex file formats, layout engines and localization requirements. The practical result was a lower coordination cost: contributors could understand where work belonged, how changes were evaluated and what information the wider community needed to stay aligned.
The technical or organizational model
OpenOffice.org combined substantial Sun engineering with outside community contributions. The arrangement brought resources to an unusually complex application category but also left important infrastructure, trademarks and roadmap authority closely associated with one corporate sponsor. [2] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
Corporate sponsorship and dependence
Full-time corporate engineering accelerated development while making contributors sensitive to who controlled infrastructure and long-term direction. The practical result was a lower coordination cost: contributors could understand where work belonged, how changes were evaluated and what information the wider community needed to stay aligned.
How collaboration actually worked
When Oracle acquired Sun, many contributors became uncertain about the project’s future. In September 2010 a group announced The Document Foundation and a fork named LibreOffice, using the legal right to copy and continue the code under a new governance model. [3] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
Forking as governance
The fork did not need permission to reuse open code, but it did require contributors to rebuild project identity, release systems and trust. The practical result was a lower coordination cost: contributors could understand where work belonged, how changes were evaluated and what information the wider community needed to stay aligned.
The milestone that made the idea visible
LibreOffice rapidly established its own releases and contributor infrastructure. The Document Foundation describes the project as a continuation of the OpenOffice.org community under independent nonprofit stewardship rather than merely a rebranded build. [4] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
Building a new center
LibreOffice had to demonstrate quickly that the new institution could ship stable software and attract downstream distributions. The practical result was a lower coordination cost: contributors could understand where work belonged, how changes were evaluated and what information the wider community needed to stay aligned.
Governance became part of the software
The Document Foundation became the institutional center for trademarks, finances and community governance. This separated long-term project control from any single office-suite vendor and gave contributors a formal organization to support the fork. [5] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
The project exposed difficult tradeoffs
Oracle later contributed OpenOffice.org to the Apache Software Foundation, producing a second related open-source office suite. The split exposed the reality that code can be legally forked while names, infrastructure and community legitimacy follow different paths. [1] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
The long-term influence outlived one release
Linux distributions and developers moved quickly toward LibreOffice, giving the fork users, patches and visibility. The developer community then pursued code cleanup, compatibility improvements and a faster release cadence through the new project’s infrastructure. [2] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
Why this belongs in open-source history
The OpenOffice.org-to-LibreOffice transition belongs in collaboration history because it shows forking as a constitutional mechanism. Open licensing made exit possible, but social coordination determined whether the new project became a viable center of development. [3] This mattered because the project was not only producing code; it was also defining a repeatable way for people outside one employer or institution to participate. The design therefore has to be read at two levels: the immediate software problem and the collaboration structure that made the solution sustainable.
LibreOffice also shows how downstream communities influence the success of a fork. Linux distributions already packaged the office suite, maintained patches and communicated with upstream developers. When many of them adopted LibreOffice, the fork immediately gained users, bug reports and credibility. An open-source project is therefore larger than its central repository; packagers, translators and extension authors can determine where the practical center of gravity moves.
Works Cited
- 01Apache OpenOffice — Project History openoffice.org
- 02The Document Foundation — 2010 Announcement documentfoundation.org
- 03LibreOffice — Who We Are libreoffice.org
- 04Apache Incubator — OpenOffice.org incubator.apache.org
- 05LibreOffice — Developers libreoffice.org
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead