Welcome to The Document Foundation Planet

This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.

To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.


Saturday
06 December, 2025


face

A modern C++ wrapper for the Firebird database API.Documentation | Repositoryfb-cpp provides a clean, modern C++ interface to the Firebird database engine. It wraps the Firebird C++ API with RAII principles, smart pointers, and modern C++ features.Features Modern C++: Uses C++20 features for type safety and performanceRAII: Automatic resource management with smart pointersType Safety:


Friday
05 December, 2025


[en] Michael Meeks: 2025-12-05 Friday

13:58 UTC

face
  • Mail chew, worked through a growing admin backlog. Great TTT from Kendy on Collabora Office on Mac.
  • Published the next strip on trying to please everyone:
    The Open Road to Freedom - strip#46 - trying to please everyone

face

LibreOffice Conference 2026 in Pordenone, Italy, and LibreOffice Conference 2027 in Gothenburg, Sweden

LibreOffice Conference 2026 will be organised by PNlug (Pordenone Linux User Group) and the University of Pordenone in the city of Pordenone, on the university campus.

The conference will begin on Thursday, 10 September and will end on the morning of Saturday, 12 September with the usual closing session.

In the days leading up to the conference, there will be a series of internal meetings and the usual community meeting on the afternoon of Wednesday 9 September.

Of course, all the details of the conference, the call for papers, and the final programme with all the side events will be announced during 2026 on this blog and on the conference website.

LibreOffice Conference 2027 will be organised in Gothenburg, Sweden, by the local community led by Leif-Jöran Olsson, who will be involved in the organisation of the 2026 conference to familiarise himself with the process.

Again, all details will be announced on this blog and on the conference website starting in the last quarter of 2026.


Thursday
04 December, 2025


face

After submitting a patch to LibreOffice Gerrit, one has to wait for the continuous integration (CI) to build and test the changed source code to make sure that the build is OK and the tests pass successfully. Here we discuss the situation when one or more CI builds fail, and how to handle that.

Why Build and Test on CI?

After you submit code to LibreOffice Gerrit, reviewers have to make sure that it builds, and the tests pass with the new source code. But, it is not possible for the reviewers to test the code on each and every platform that LibreOffice supports. Therefore, Jenkins CI does that job of building and testing LibreOffice on various platforms.

This can take a while, usually 1 hour or so, but sometimes can take longer than that. If everything is OK, then your submission will get     Verified +1    .

CI Platforms for LibreOffice

Currently, these are the platforms used in CI:

  • Linux / GCC:  gerrit_linux_gcc_release
  • Linux / Clang: gerrit_linux_clang_dbgutil
  • Android Viewer: gerrit_android_x86_64 and gerrit_android_arm
  • Windows: gerrit_windows_wsl
  • macOS: gerrit_mac

Some of the tests are more extensive, for example Linux / Clang also performs additional code quality checks with clang compiler plugins. Also, UITests are not run on each and every platform.

Jenkins LibreOffice CI

LibreOffice CI uses Jenkins

Why Failures Happen and How to Fix?

There can be multiple reasons for why a CI build fails, and give your submission    Verified -1   . These are some of the reasons, and depending on the reason, solution can be different.

1. Your code’s syntax is wrong and compile fails

In this case, you should fix your code, and then submit a new patch set. You have to wait again for a new CI build.

2. The code’s syntax is OK, but it is not properly formatted

You should refer to the below TDF Wiki article and use clang-format tool to format your code properly.

3. Your code’s syntax is OK, but it logically not OK and fails some tests.

In this case, you should try fixing your code logic, and run the tests that fail and make sure they pass. After that, you may send a new patch set and wait for a new CI build.

4. Your code’s syntax and logic is OK, but some machine fails for other reasons like their disk being full or other software/hardware failures or hiccups

In this case, usually resuming the build can be a good option. You may ask on #libreoffice-dev or #tdf-infra IRC rooms for such a resume, or request access, if you submit many patches.

Resume CI build

Resume build in LibreOffice CI

5. Your code’s syntax and logic is OK, but there are issues from other patches.

In this case, intervention from other LibreOffice developers is needed. Informing people on #libreoffice-dev can help, and then you have to re-base your submission in case new patches fix the build issue.

Final Notes

The best way to know the reason of the build failure is to look into


[en] Michael Meeks: 2025-12-04 Thursday

21:00 UTC

face
  • Mail chew, tech. planning call, new Collabora Office launch retrospective call. Lunch.
  • Sync with Lily, Laser, partner slide sync, drove to Cambridge, good to catch-up with people, finance team call. Christmas dinner with lots of the wider Collabora team, good to meet Tina.

face

The Document Foundation (TDF), la organización sin fines de lucro detrás de LibreOffice, continúa fortaleciendo su equipo de desarrollo con nuevos roles orientados a mejorar el diseño y la experiencia de usuario del proyecto. Hoy, nos complace presentar a Dan …


face

I fetched the release notes for FirebirdSQL/php-firebird and made a concise summary of the user-visible changes and upgrade impact for versions from PHP Firebird 5.0.2 up through 6.1.1-RC.2.I retrieved the release entries for 5.0.2, 6.1.1-RC.0, 6.1.1-RC.1 and 6.1.1-RC.2 and distilled the highlights and upgrade impact into a short, actionable summary below.Summary of changes (5.0.2 → 6.1.1-RC.2)-


face

Photo of Dan Williams

The Document Foundation is the small non-profit entity behind LibreOffice. It oversees the project and community, and is now expanding with new developer roles. So let’s say hello to Dan Williams, who joins the team to work on design and user interface (UI) improvements, with an initial focus on macOS:

Tell us a bit about yourself!

I’m from the USA, have lived on both US coasts at various times, and now live back in the “midwest” where I grew up.

I was previously a software engineer, team lead, and manager at Red Hat for more than 20 years. In that time I’ve worked on a large variety of projects, from local networking to cloud networking to desktop software. I spent two years helping build the One Laptop Per Child software stack which was an eye-opening experience from a UI and design perspective. I believe passionately in free and open-source software; all the code I’ve written so far in my career is open-source.

Oddly enough, I’m not new to the LibreOffice community; I was an OpenOffice contributor and co-founded the NeoOffice port to Mac OS X (now called macOS). That led to being hired by Red Hat to package and improve OpenOffice for Fedora and Red Hat Enterprise Linux, where I helped start the 64-bit port and realize the Native Widget Framework that’s still used in LibreOffice today. I eventually handed my Red Hat OpenOffice duties over to Caolán McNamara (now at Collabora) and moved on to networking. I still recognize quite a few of our community members who I worked with before!

Outside of office software I’m the maintainer of the ModemManager WWAN software stack and I seem to have developed a hobby of collecting LTE and 5G base stations. I enjoy playing with hardware (especially if it runs Linux), baking and cooking, building large structures out of wood, and occasionally brewing beer in my basement.

What’s your new role at TDF, and what will you be working on?

A significant part of my new role will echo my early OpenOffice contributions: Mac! I’ll convert the last bits of Carbon API into modern Cocoa ones. This old code involves some pretty core functionality like popup menus and key modifier detection so it’s going to be tricky but we need to do it. Nobody knows how much longer Apple’s going to support HIToolbox but I’d like to be prepared. I’m also going to improve general Mac usability and experience; I’ve been using LibreOffice on macOS since the beginning so I’m familiar with its rough edges.

LibreOffice screenshot, running on macOPS

But the Mac isn’t the only platform so I’ll be driving user interface improvements and fixing annoying bugs everywhere else too, regardless of platform or visual backend. I also look forward to working with the LibreOffice Design community to try out new ideas and see what sticks.

I enjoy the challenge of working throughout the entire codebase, from


face

The Firebird Book, Second Edition is made publicly available via the IBPhoenix digital store. Everyone can download the complete edition free of charge — no strings attached.If you'd like to support Helen’s legacy and the Firebird community, there is an optional pay‑what‑you‑like contribution. Funds will support the organization of the Helen Borrie Memorial Award, recognizing individuals with


Wednesday
03 December, 2025


[en] Michael Meeks: 2025-12-03 Wednesday

21:00 UTC

face
  • Early partner call, sync with Dave, then Ben, then Patrick & Kevin.
  • E's maths progress review call. Interview, weekly sales call, sync with Philippe.
  • All Saints band practice in the evening.

face

LibreOffice 26.2 se lanzará como versión final a principios de febrero de 2026 (consulte el Plan de lanzamiento), siendo LibreOffice 26.2 Alpha1 la primera versión preliminar desde que comenzó el desarrollo de la versión 26.2 a principios de junio …


face

Esta nueva versión del estándar de formato de documento nativo de LibreOffice marca el vigésimo aniversario del único formato de documento abierto para aplicaciones de oficina

Berlín, 3 de diciembre de 2025. The Document Foundation anuncia que OASIS Open (…


face

ODF 1.4 Approved as Oasis Open StandardThis new version of the native LibreOffice document format standard marks the 20th anniversary of the only open document format for office applications

Berlin, December 3, 2025 – The Document Foundation announces that OASIS Open (www.oasis-open.org), the global open-source and standards organisation, has approved the Open Document Format (ODF) for office applications v1.4 as an OASIS standard, which is the organisation’s highest level of ratification.

The release of ODF v1.4 coincides with the 20th anniversary of ODF’s adoption as an OASIS Standard. Since 2005, ODF has served users as a vendor-neutral, royalty-free format for office documents, ensuring that files remain readable, editable and interoperable across platforms.

Several governments and international organisations, including NATO, the European Commission and countries across multiple continents, have mandated ODF for their operations worldwide.

ODF v1.4 maintains full backward compatibility and improves developer documentation, adds better support for assistive technologies for accessibility, improves professional document formatting and visual design capabilities, and expands features for data analysis and technical documentation. These updates reinforce the Open Document Format’s position as a comprehensive solution for office productivity and document creation.

“ODF provides a vendor-neutral foundation for office productivity and collaboration. With v1.4, the standard continues to evolve, supporting cloud collaboration, richer multimedia, and standardised security,” said Svante Schubert, Open Document Format’s TC Co-Chair. “Looking ahead, ODF is moving beyond document exchange towards standardised, semantic, change-based collaboration, enabling the meaningful sharing of interoperable changes across platforms.”

ODF v1.4 safeguards digital sovereignty by removing a single vendor’s control over documents and returning it to the community, to allows individuals and enterprises to independently decide how and with whom to share content, preventing it from being analysed for commercial purposes or potentially shared without the legitimate owner’s knowledge.
Like all other versions of the standard format, ODF 1.4 is based on an XML schema that complies with simplicity and readability guidelines, making files much more robust and secure than those commonly found on the market.

Overall, this is another significant step towards transparency, openness and digital sovereignty, thanks to the collaborative efforts of open-source software developers, advocates and users.
The finalized four-part specification of ODF v1.4 can be found in the OASIS library by clicking here: docs.oasis-open.org/office/OpenDocument/v1.4/os/.

The announcement mentions OASIS sponsors who have not contributed to the development of ODF 1.4, whereas The Document Foundation, which funded the development of the standard alongside companies such as Microsoft and has always advocated for it, is not mentioned at all. Unfortunately, business is business, even when it comes to open standards.

ODF 1.4 New Features

General

  • The writing direction specification has been expanded and clarified.
  • Complex backgrounds, such as colour gradients or hatching, can now be applied to a wider range of objects.
  • Objects can be marked as “decorative” to support accessibility technologies.
  • Shapes can now contain not only simple text and lists, but also tables.
  • The method for specifying

face

LibreOffice 26.2 will be released as final at the beginning of February, 2026 ( Check the Release Plan ) being LibreOffice 26.2 Alpha1 the first pre-release since the development of version 26.2 started at the beginning of June, 2025. Since then, 4651 commits have been submitted to the code repository and 676 bugs were set to FIXED in Bugzilla. Check the release notes to find the new features included in this version of LibreOffice.

LibreOffice 26.2 Alpha1 can be downloaded for Linux, macOS and Windows, and it can be installed alongside the standard version.

In case you find any problem in this pre-release, please report it in Bugzilla ( You just need a legit email account in order to create a new account ).

For help, you can contact the QA Team directly in the QA IRC channel or via Matrix.

LibreOffice is a volunteer-driven community project, so please help us to test – we appreciate it!

Happy testing!!

Download it now!


face

Writer recently got a new markdown import option to take styles from a template, leading to much prettier output when converting markdown to PDF, DOCX or ODT.

This work is primarily for Collabora Online, but the templating feature is available in desktop Writer as well.

Motivation

A previous post mentioned recent improvements to the markdown import/export in Writer.

But if you convert some markdown to e.g. PDF, all the headings just have the default look, wouldn't it be nice to take your organization template and add colors and other formatting there, automatically?

Also, wouldn't it be nice if you could paste as markdown in COOL or copy the current selection as markdown? Which would enable all sorts of interesting use-cases, like using an external API to turn the selection into a summary or translating it to a different language.

Results so far

Here is a sample input markdown:

# heading 1

body text

Here is how it looks like if you template it using the core.git sw/qa/filter/md/data/template.docx sample:

PDF result: templated

curl invocation for this:

curl -k -F "data=@/path/to/test.md" -F "template=@/path/to/template.docx" -F "format=pdf" -o out.pdf https://localhost:9980/cool/convert-to

Or example desktop command-line:

soffice --infilter='Markdown:{"TemplateURL":{"type":"string","value":"./template.ott"}}' test.md

While it would look like this by default:

PDF result: default

The other part is the PostMessage API of COOL, if you want to copy and paste as markdown. What's newly possible:

  • Copy the current selection: set MessageId to Action_Copy and the value to {"Mimetype": "text/markdown;charset=utf-8"}
  • Paste at the current cursor position: set MessageId to Action_Paste and the value to something like {"Mimetype": "text/markdown;charset=utf-8", "Data": "foo _bar_ baz"}

You can read more about the PostMessage API in the COOL SDK.

How is this implemented?

If you would like to know a bit more about how this works, continue reading... :-)

As usual, the high-level problem was addressed by a series of small changes. Core side:

Online side:

Want to start using this?

You can get a development edition of Collabora Online 25.04 and try it out yourself right now: try the development edition. Collabora intends to continue supporting and contributing to LibreOffice, the code is merged so we expect the core of this


Tuesday
02 December, 2025


[en] Michael Meeks: 2025-12-02 Tuesday

21:00 UTC

face
  • Up early, new Collabora Office team call - nice. Planning call, sync with Laser, lunch.
  • Call with Jim, sync with Anna, chart team call, sync with Laser.

face

 

The Document Foundation (TDF) es la entidad sin fines de lucro que respalda el proyecto LibreOffice. Recauda donaciones de los usuarios y cuenta con un pequeño equipo que da soporte y coordina a la comunidad mundial que desarrolla el software. …


Monday
01 December, 2025


[en] Michael Meeks: 2025-12-01 Monday

21:00 UTC

face
  • Still feeling groggy; early meeting on a11y testing. Sync with Miklos, Thorsten, lunch, signed documents, marketing content call.
  • Sync with Naomi, Pedro & Eloy.
  • Dinner, games with E&H&J, music with H. bed.

face

TDF logo and words Code of Ethics

The Document Foundation (TDF) is the non-profit entity behind the LibreOffice project. It collects donations from users, and employs a small team to support and coordinate the worldwide community that makes the software. In TDF there are various bodies including the Board of Directors, Membership Committee, and the Board of Trustees:

Diagram of structure of TDF bodies

These foundation bodies are guided by a set of policies, and now the Board of Directors has voted on a Code of Ethics and Fiduciary Duties. The code ensures that members of the Board of Directors “strive to speak and act with the mission and effectiveness and the best interest, and only the interest, of the foundation in mind.” See here for the results of the vote.

Click here for the full Code of Ethics and Fiduciary Duties


Sunday
30 November, 2025


[en] Michael Meeks: 2025-11-30 Sunday

21:00 UTC

face
  • Cold advancing down the throat; All Saints in the morning. Rested with J. much of the day and tried to recover.

Saturday
29 November, 2025


[en] Michael Meeks: 2025-11-29 Saturday

21:00 UTC

face
  • Up earlyish, J. & H. off to see B&A. Plugged away at tasks - replaced failed bathroom extractor fan with a rather better Airflow model with sealing iris.
  • Mounted new Wireless Reolink security camera to watch the road more effectively, good to have built-in SD cards.
  • Plugged away at E-mail, got new standing desk thing mostly sorted out - fun.
  • E. had a dinner party in the evening with some of her friends, lovely.

Friday
28 November, 2025


[en] Michael Meeks: 2025-11-28 Friday

21:00 UTC

face
  • Up early, drove to Ipswich Hospital to see B. spent some time with him, on to see A. - also unwell; got some shopping & an F&C lunch.
  • Back to see Bruce, got him F&C too, good to see him eat, drove home late.
  • J. out to Church Ladies dinner, ate with E. - relaxed.

face

Los flujos de datos confiables, las firmas verificables y las estructuras predecibles son esenciales en los sistemas de identidad digital, que intervienen en todos los aspectos de la vida digital moderna. Estos sistemas autorizan transacciones, confirman solicitudes y garantizan el …


face

Tokio, Japón – La LibreOffice Asia Conference 2025 se llevará a cabo los días 13 y 14 de diciembre de 2025, en la sede de Internet Initiative Japan Inc., ubicada en Iidabashi Grand Bloom, Tokio. El evento reunirá a …


face

Reliable data flows, verifiable signatures and predictable structures are essential for digital identity systems, which touch every aspect of modern digital life. They authorise transactions, confirm requests and guarantee security policies.

In this context, the Open Document Format (ODF) offers a transparent, computer-readable foundation for verifying the authenticity of documents and ensuring their long-term integrity.

Each ODF file is a structured ZIP container with a consistent internal layout. It contains a set of XML files that are always located in the same position. These files include meta.xml for metadata, manifest.xml for the list of files and relationships, content.xml for document data and styles.xml for presentation rules. The files are either ODT (text), ODS (spreadsheets), ODP (presentations) or ODG (drawings).

Because everything is in XML format and in the same location, identity systems can analyse the content without searching for it as they would with OOXML files, which vary greatly depending on the application used to create them. Identity systems can therefore focus on specific parts of a file rather than scanning raw binary blocks, which are present in OOXML files.

This is important for signing, integrity validation, metadata extraction and policy enforcement. When documents move from one identity platform to another, APIs can map ODF elements in a stable manner, reducing ambiguity and improving verification speed.

Document Signing

ODF supports the XML Signature and XML Encryption standards via the META-INF/documentsignatures.xml file. This file can contain multiple independent signatures, each relating to specific parts of the document. The signature refers to an explicit path within the ZIP container, making automatic verification easier and avoiding confusion caused by false errors resulting from layout changes.

Each document can contain user signatures, organisational seals, timestamps, and workflow attestations. Each signature can also contain its own certificate chain, revocation information, and policies.

ODF is compatible with standard X.509 certificates, enabling the use of national eIDAS identification systems and corporate PKI systems. Verification pipelines can apply the same trust rules used for signed emails or encrypted communications.

Interoperability and Identity Federation

Digital identity works best when it is portable. ODF’s openness supports this by avoiding vendor-specific binary constructs. Any identity framework can be integrated with ODF because its schema is public and stable, its structure is predictable, and there are no proprietary validators.

In federated identity ecosystems, such as cross-border government services or multi-cloud enterprise configurations, ODF reduces friction and ensures that documents remain compatible, even when authentication systems differ.

Long-Term Signature Validation and Archival Use

In some cases, identity systems must verify a document signed many years earlier, which requires long-term validation. ODF supports long-term authentication because its XML structure is future-proof: it can store timestamps, revocation data and certificate chains, and it avoids vendor-specific cryptographic formats.

In legal, regulatory and archival contexts, this aspect is more important than speed. Formats that rely on proprietary rendering engines risk becoming unreadable over time, whereas ODF remains readable, even many years later.

ODF in Zero Trust Workflows

In Zero


face

Conference logo and picture of Japan

Tokyo, Japan – The LibreOffice Asia Conference 2025 is scheduled to take place on December 13-14, 2025, at the Internet Initiative Japan Inc. headquarters in Iidabashi Grand Bloom, Tokyo. The event will bring together the Asian Open Source community to discuss developments in LibreOffice, the OpenDocument Format (ODF), and related technologies.

The conference features a diverse lineup of international speakers covering various technical and community-oriented topics. Below is an overview of the sessions organized by the speakers’ regions.

🇮🇩 Indonesia: Massive Contribution and Regeneration

The Indonesian delegation brings a strong spirit of sharing. Diah Asyanti will recount the inspiring journey of open document adoption by educators in Indonesia, a significant step for the education sector. Community sustainability is also a key focus for Ahmad Haris, who will thoroughly explore the challenges and strategies for regenerating young talent in FOSS projects.

Equally engaging, Rania Amina invites participants to dive into the fun side of contributing to LibreOffice, debunking the myth that contribution is difficult or boring. For technical enthusiasts, Sartika Lestari is ready to share practical tips on LibreOffice automation using Python ScriptForge.

🇯🇵 Japan: Host with Technical and Community Focus

As the host, the Japanese community presents topics highly relevant for both new users and developers. Kenta Ito & Yuichi Kojima will lead a beginner-friendly session designed to help users transition smoothly to LibreOffice Writer.

On the innovation front, Koji Annoura will introduce “Dana Language,” an intriguing new approach to intent-driven automation. Meanwhile, Saburo Yoshida will open perspectives on how contributing to LibreOffice is inclusive and not limited to programming skills alone.

🇩🇪 Germany: Standards and Business

Perspectives from Europe, specifically Germany, will enrich participants’ understanding of standards and business. Svante Schubert will emphasize why the OASIS OpenDocument Format (ODF) standard is crucial for long-term interoperability. Complementing this, Lothar K. Becker will dissect how Open Source has become a strategic competitive factor for the private sector.

🇹🇼 Taiwan: Customization and Debugging

Experts from Taiwan are set to share deep technical techniques. Jia, Jun Xu will demonstrate how customizing key components can significantly boost productivity. For those who love problem-solving, Buo-ren Lin & Po-Yen Huang will introduce the unique “Vibe-debugging” method to tackle bugs in LibreOffice.

🌏 Other International Participation

The conference is further colored by speakers from around the globe. From India, Manish Bera will share effective strategies for growing the LibreOffice community. Tomaž Vajngerl from Slovenia will showcase cutting-edge features in Collabora Online.

Important updates regarding the community and ODF status in South Korea will be delivered by DaeHyun Sung. Finally, Eyal Rozenberg will raise vital issues regarding non-Western script support, uniting the interests of RTL and CJK language communities.

The LibreOffice Asia Conference 2025 aims to foster collaboration among Asian communities and promote the advancement of free and open-source office software.

Registration and Participation Details

Participation in the conference is free of charge, but advance registration is required via the Connpass platform.

  • Registration Link
  • Fee: Free
  • Venue: Internet Initiative Japan Inc. Head Office, Iidabashi Grand Bloom, Tokyo

Important Notice for International Participants

The Connpass registration system


Thursday
27 November, 2025


[en] Michael Meeks: 2025-11-27 Thursday

21:00 UTC

face
  • Tech. planning call, admin, lunch, sync with Laser, pulled more pieces together.
  • Published the next strip: Changing the guard:
    The Open Road to Freedom - strip#45 - changing the guard
  • Sync with Lily, J. off to see B. in hospital. Dinner with E. Ordered parts to replace and upgrade extractor fans.

Wednesday
26 November, 2025


face

Just a short personal note to say how super excited I am to get our very first release of a new Collabora Office out that brings Collabora Online's lovely UX - created by the whole team to the desktop. You can read all about it in the press release. Please note - this is a first release - we expect all manner of unforseen problems, but still - it edits documents nicely.

Collaborative development

The heros behind the scenes

There has been a huge amount of work behind the scenes, and people to say thank-you to. Let me try to get some of them:

  • First off - thanks to Jan 'Kendy' Holesovsky and Tor Lillqvist (who came out of retirement to create yet another foundational heavy-lift for FLOSS Office. I can't say how grateful we are for your hard work here on Mac and Windows respectively.
  • Then after the allotropia merger we had Thorsten Behrens to lead the project, and Sarper Akdemir to drive the Linux front-end.
  • Towards the end of the project we were thrilled to expand things to include a dream-team of FLOSS engineers to fix bugs and add features ...
  • Thanks to Rashesh Padia for the lovely first-start WebGL slideshow presentation added to Richard Brock's content skills.
  • Thanks to Vivek Javiya for building a new file creation UI with Pedro Silva's design skills here and elsewhere.
  • Lots of bug fix and polishing work from Parth Raiyani, and Jeremy Whiting (who also did multi-tabbed interface on Mac), and to Stephan Bergmann for digging out and clobbering the most hard-core races and horror bugs that we had hidden, Caolán McNamara too who made multiple documents work, and fixed crashes and multi-screen bits.
  • With Hubert Figuière making the flatpak beautiful, and of course the indomitable Andras Timar doing so much amazing work getting all of the CI, release-engineering, app-store, translation pieces and also bug-fixing done and completed in time.
  • Thanks too to our marketing team: from Chris Thornett getting the press briefing into a good state and multiplexing quotes left and right, to Richard Brock creating beautiful blog output, to Asja Čandić socializing it all, with Naomi Obbard leading the charge.
  • Thanks also to Darshan Upadhyay for packing the community website with hard-working-beaver goodness, updated community page, as well as new build instructions, FAQ, supported pages, and much more.
  • Thanks to all of our supporters who say nice things about us, and of course to so many translators who contribute to making Collabora Online great - hopefully now the strings are all public it should be easy to expand coverage.

This is an outstanding result from so many - thank you!

What is next technically ?

There are lots of things we plan to do next, but there is so much that can be done. First - merging the work into our main product branches - and at the same time sharing much more of the code across platforms. We have some features in the pipeline already - starting to take more advantage of platform APIs for much


[en] Michael Meeks: 2025-11-26 Wednesday

21:00 UTC

face
  • Mail chew, something of a frenzy of activity. Wrote up some under-the-hood-ness for the new Collabora Office.
  • Wrote up the Collabora Office release pieces, multiplexed lots of E-mail and chat around it.
  • Band practice in the evening.

Tuesday
25 November, 2025


[en] Michael Meeks: 2025-11-25 Tuesday

21:00 UTC

face
  • Up early, breakfast, exciting day at the (packed) Nextcloud Enterprise Day, lots of great questions, handed out dozens of hard-working beaver mascots, quick-start guides, and showed off the great work the team has been doing.
  • Caught up with lots of old friends, got introduced to PechaKucha as a concept: 75 slides in 20 minutes is perhaps extreme: if only we did less interesting stuff, we could have fewer slides.
  • Train to AMS, worked on new Collabora Office pieces with the team before the flight; flew, drove, worked at home, bed.

Older blog entries ->