LibreOffice is a worldwide project made up of hundreds of people: volunteers, developers at ecosystem companies, and the 18-person team at The Document Foundation (the non-profit entity that coordinates the project and community). So, what has the team been working on recently? Here’s a quick summary:
Release Engineering
- Tagged, built, and distributed LibreOffice 26.8.0 Release Candidate 2
- Enabled MAR updates for cross-updates from 25.8.7 and 26.2.4 to 26.2.5
- Reviewed patches
- Tested new Windows build bots in production
- Investigated and fixed incorrect permissions in daily Debian packages
Scripting
- Investigated an extension developer’s issue exporting BASIC macros as an extension
- Identified a debug-build assertion that does not appear to affect release builds
- Added a UI test to help prevent future regressions in macro export
Code and Accessibility
- Discussed proposed accessibility improvements on the LibreOffice accessibility mailing list
- Analyzed and fixed tdf#172831: customized NotebookBar tab names were not localised after upgrading
- Released LibreOffice Viewer for Android 26.2.5 on Google Play, F-Droid, and the Meta Horizon Store
- Discussed tdf#172885, a LibreOffice-specific Qt theme/style. Explored an upstream Qt stylesheet-environment-variable approach, then implemented LibreOffice command-line support for setting the stylesheet
- Posted and reworked the macOS-specific parts of the Qt VCL work
- Reworked the changes in response to comments, then merged them
- Worked on generalising macOS scaling patch
- Made the Reset button dialog action ID well-known across the codebase
QA
- Announced LibreOffice 26.8 RC1 availability for testing
- Upgraded external libraries:
- NSS to 3.126
- libffi to 3.7.1
- Improved automated tests:
- Factored common code from
CppunitTest_sc_swarmsolvertest
- Added
ARRAYTOTEXT
function tests asFunctionsTest
- Factored common code from
- Fixed crashes and warnings:
- Fixed a null-pointer dereference warning in Writer
- Fixed a crash in
ThemeExport::write
- Fixed a crash in
OutMarkdown_SwTableNode
- Tested and commented on Qt6 style and theming work for tdf#172885
- Completed hiring tasks and code reviews
- Investigated regressions involving CJK font names and the CJK bullets gallery
- Fixed two build/SDK issues:
- Fixed a build issue with Visual Studio 2026 18.7.0
- Fixed missing cross-platform .NET binding files in the SDK (tdf#165585)
- Continued work toward resolving headless Windows/fontconfig build issues required for Qt6 on Windows
Mentoring
- Reviewed six substantial patch submissions
- Completed GSoC mentor tasks
Design
- Triaged Bugzilla tickets
- Participated in the weekly UX and ESC meetings
- Published extensions and managed comments
- Supported community growth through the @libodesign social media account
- Completed several design reviews
- Prepared the Base survey
- Contributed patches:
- tdf#115805: corrected increments in numbering dialogs
- tdf#172739: harmonized NotebookBar tab order
Documentation
- Updated online Help with fixes for Master, 26.2, and 25.8
- Updated Help pages through bug triage, contributor patch reviews, fixes, and housekeeping
- Contributed Help improvements, including:
- Adjusted left margins for paragraphs in tables
- Refactored the AutoCorrect Options page
- Updated documentation for “To page” anchoring
- Added “Page Break” to Find & Replace attributes
- Reverted removal of “Page Style” from Find & Replace attributes
- Muted localisation processing in selected Python and BASIC code lines
- Supported ongoing community updates to the Guides
- Helped newcomers
- Worked on the Bookshelf project, including sanitising the Impress Guide
Marketing
- Announced and promoted new TDF members and the new marketing position
- Maintained social media activity, updates, and responses
- Coordinated conference logistics and prepared the first conference-program draft
- Drafted sections of the TDF Annual Report 2025
- Updated journalists’ mailing lists and database
- Published blog posts about ODF and maintained the blog
- Monitored donations, downloads, media clippings, and download-support requests
- Managed budget-related activities
- Worked on preparations for LibreOffice 26.8 release
So that’s what the team is working on – and this is all thanks to your donations, which help to pay the team members. But as mentioned, this is just a small part of the LibreOffice project activity – the biggest work is being done by hundreds of other people around the world. Thanks to all of you 😊
Facts Only
The Document Foundation is a non-profit entity coordinating the LibreOffice project.
The coordination team consists of 18 people.
LibreOffice 26.8.0 Release Candidate 2 was built and distributed.
LibreOffice Viewer for Android 26.2.5 was released on Google Play, F-Droid, and the Meta Horizon Store.
MAR updates were enabled for cross-updates from 25.8.7 and 26.2.4 to 26.2.5.
NSS was upgraded to 3.126 and libffi to 3.7.1.
The TDF Annual Report 2025 is currently being drafted.
Visual Studio 2026 18.7.0 build issues were resolved.
A Base survey is in preparation.
The project involves hundreds of volunteers and developers from ecosystem companies.
Executive Summary
LibreOffice is currently managed through a hybrid model involving a small professional core of 18 individuals at The Document Foundation, supported by a global network of volunteers and corporate developers. Recent activity is concentrated on the rollout of version 26.8, including the distribution of Release Candidate 2 and the preparation of related marketing and release materials. Technical efforts are diversified across several fronts: stabilizing the Android viewer, updating external libraries like NSS and libffi, and resolving platform-specific build issues for Windows and macOS.
Beyond core engineering, the project is maintaining its ecosystem through documentation updates, UX design reviews, and the management of community extensions. Governance and sustainability efforts are evident in the drafting of the 2025 Annual Report and the ongoing monitoring of donations. While the professional team handles coordination and specific high-priority tasks, the bulk of the development work remains distributed across the wider community.
Full Take
The strongest version of this narrative is a transparent "proof of work" update, designed to demonstrate accountability to donors by mapping financial contributions to specific technical and administrative outputs. It portrays a healthy, functioning open-source ecosystem where a non-profit entity provides the necessary scaffolding for a massive, decentralized volunteer effort.
The narrative relies on a high volume of granular, technical detail to establish legitimacy. By listing specific bug IDs (tdf#172831) and library versions, the communication shifts the reader's focus from "what is the value of this project" to "look at how much is being done." This is a standard transparency pattern in non-profit management, utilizing technical density to signal competence and diligence.
Patterns detected: none
The driving paradigm is the "Open Source Cathedral and Bazaar," where the TDF acts as the coordinating center for a chaotic but productive periphery. The unstated assumption is that the continuation of this output is directly contingent upon continued donor funding.
For the user, this reinforces the agency of the community over proprietary software locks, though it also highlights the fragility of relying on a small coordinating team. The second-order consequence is a dependency on a specific non-profit's administrative health to ensure the viability of the software.
If this were an influence campaign, a bad actor would use "technical obfuscation"—flooding a report with jargon to hide a lack of actual progress or to mask the diversion of funds. However, the specific nature of the tasks mentioned (e.g., fixing null-pointer dereferences and updating help margins) is too mundane and typical of software maintenance to be a manufactured facade.
Bridge Questions:
1. How does the ratio of paid staff to volunteers affect the long-term roadmap of the project?
2. In what ways does the reliance on donations influence which features are prioritized over others?
3. What happens to the project's stability if the coordinating entity (TDF) faces a leadership or funding crisis?
Sentinel — Human
The text reads like a summary compiled from a structured, human-managed project update, exhibiting specific technical jargon and an informal closing tone consistent with community reporting rather than pure synthetic generation.