Category: Interviews

Following our interviews with Caolán McNamara at Red Hat and Thorsten Behrens at allotropia, today we’re talking to Michael Meeks from Collabora Productivity:

Tell us a bit about yourself!

I’m Michael Meeks, a Christian, husband and enthusiastic open source developer. I run Collabora’s Office division with the assistance of an amazing team – leading our Collabora Online and Office products, and supporting customers and partners. I’ve served as a Director of the The Document Foundation from its founding until recently, and have contributed to both the OpenDocument Format and OOXML standardization.

I’d started some decades ago working on the Linux desktop in the GNOME project around the Gnumeric spreadsheet, first as a volunteer, then for Ximian – which was involved in the open-sourcing of OpenOffice.org. Since then, I’ve been involved with improving the codebase, although the name of my employer has changed from Ximian, Novell, Attachmate, Micro Focus, SUSE – and finally being spun out alongside a brave and talented subset of the SUSE LibreOffice team to Collabora Productivity some nine years ago.

What does Collabora Productivity provide in the LibreOffice ecosystem?

One big piece we do is improving the awesome LibreOffice Technology core engine / APIs, and performance for Collabora Online – which provides a real alternative to Microsoft Office 365 – with collaborative editing in the browser. We spend time working hard on integrations with popular open source products like Nextcloud, ownCloud, Seafile, EGroupware, and proprietary ones such as HiDrive, Filr – as well as helping hosting providers like Strato provide LibreOffice Technology to their users en-masse.

Around Collabora Online, we have a mission to allow you to control your documents. That means full control from open source software, open standard file formats, through to on-premise hosting, and full network control. It is encouraging to see the growing consensus these days between e.g. The European Pirate Party (enthusiastic Collabora Online users) talking positively about the importance of Digital Sovereignty, and at another pole – for instance, the head of the UK’s MI6 warning on the BBC:

“The data-trap is this: that if you allow another country to gain access to really critical data about your society, over time that will erode your sovereignty.”

For Collabora’s customers, we also take a new LibreOffice version each year and freeze this as our Long-Term Support (LTS) base; we create many hundreds of fixes and feature patches which we contribute up-stream, as well as back-porting the latest fixes to our enterprise branch: much as is done for an enterprise Linux distribution. We sell that toegher with services and support as Collabora Office. We also maintain a tool (Collabora OLE Automation Tool) to ease migration of vertical applications that use Visual Basic / OLE2 integration that makes LibreOffice behave like Microsoft Office via COM. In addition, we maintain Collabora Office and LibreOffice Windows Group Policy Templates – these make it easy to manage lots of LibreOffice machines via Group Policy.

Another strand of work is re-packaging Collabora Online / LibreOffice Technology as responsive mobile apps for Android and iOS, as well as Chrome OS. By delivering LibreOffice-based document editing to everyone’s browsers, PCs and mobile devices, we give people a real alternative that lets them choose their own document formats, security profile and threat model – real digital sovereignty.

What has Collabora been working on in LibreOffice 7.3?

We’ve been working on lots of things: some of the team have done a lot for interoperability, e.g. Miklos improving writer’s paragraph styling, or Dennis making charts more compatible, or Sarper re-working our PowerPoint header/footer interoperability. There is a constant stream of improvements based on customer feedback here.

Another big set of improvements in LibreOffice 7.3 are from Lubos and Noel around the performance of file opening, rendering, editing of documents as well as improving calculation threading. One particularly important piece here was the work done to very significantly improve performance of lots of editors in a single file – which has been back-ported to make Collabora Online very much faster in our latest releases.

We are looking forward to upgrading to LibreOffice 7.3 in the next months, and not having to carry these back-ports forward.

What new features are you particularly happy with?

I’ve been really pleased with the work we’ve done alongside AMD around Skia rendering – in LibreOffice 7.3 we make that the default for macOS (users, please report any problems), which for the first time allows us to share a single, modern rendering API between macOS, Linux and Windows for rendering – which is a huge step in the right direction.

What’s more: adding WebP support for images – interestingly, Firefox now requires this as a copy/paste format for images, and it’s long overdue to have this high quality format from Google supported.

Looking beyond this release, what else are you planning to do?

We work continuously on LibreOffice, all around the code from ongoing clean-ups, performance work, unit-tests (particularly important to avoid customer tickets regressing) and so on. We have a few things that are in the works currently.

Another thing that Tomaz, Sarper and Miklos will debut in LibreOffice 7.4 is the start of colour theme support for shapes, to allow us to re-style documents more deeply by changing the theme and palette. This should also help with interoperability and templating.

We’ve also added Sparkline support, providing a very pretty and useful way to quickly visualize data for LibreOffice 7.4.

You can read about the history of these from Edward Tufte.

Lubos has been working hard on jumbo sheets – allowing much larger number of columns in sheets (and more rows too) which should make interoperability much smoother for people with large spreadsheets.

And of course lots more – we’re expecting LibreOffice 7.4 to be packed with new and enhanced feature / function from the whole community – and Collabora.

Find out more

• Collabora Productivity
• Collabora Online
• Collabora Office on Twitter

LibreOffice is developed by a worldwide community, made up of volunteers, certified developers and companies in the wider ecosystem. Today we’re talking to Thorsten Behrens, who serves on The Document Foundation’s Board of Directors and works for allotropia…

Tell us a bit about yourself!

I’m Thorsten Behrens, living in Hamburg, Germany. With a great team of LibreOffice experts, I run allotropia software GmbH, which specialises in Open Source and Open Standards consulting and products.

The code and the project itself had me involved from 2001 on (then still called OpenOffice.org).

What does allotropia provide in the LibreOffice ecosystem?

We strive to be a full-service shop for all things LibreOffice. Just to list a few examples, we have helped companies to train their internal development team alongside a LibreOffice migration; we’re regularly developing bug fixes and new features for the office suite, and we’re also maintaining a number of extensions for the benefit of the entire ecosystem (e.g. the LibreOffice Eclipse development plugin, the Edit in LibreOffice Nextcloud plugin, or the LibreOffice Starter Extension).

Additionally, we’re offering LTS (long-time supported) versions of LibreOffice, via our partner CIB software GmbH. In the same vein, we also maintain customer-specific LTS branches, in case a larger organisation has decided to stick with one particular version of the suite.

And not to forget, allotropia also sponsors Michael Stahl, one of the editors of the OpenDocument Format, to keep the ODF standard evolving and keeping up with all the new LibreOffice features that need saving to disk.

What has allotropia been working on in LibreOffice 7.3?

Besides lots of smaller additions for LibreOffice 7.3, one of the highlights we’re currently working on is a port of LibreOffice to directly run in a browser – without any need for a server installation. We’re provisionally calling it LOWA – LibreOffice WebAssembly, since WebAssembly (WASM) is the underlying browser technology this is using.

Another feature we’re quite proud of, is the rewrite of LibreOffice’s old network file access code. That work was sponsored by The Document Foundation, has landed in 7.3, solved a number of long-standing problems, and at the same time got rid of over 17,000 lines of (pretty old) code.

Looking beyond this release, what else are you planning to do?

There’s just a ton of work still to do, to make the LOWA LibreOffice really usable, so that will keep us pretty busy this year. Beyond that, we’re always eager to help making the overall developer experience for LibreOffice better – that helps us too, in our daily work! Along those lines, there’s another project currently underway, called CoverRest, to bring better and nicer integration with code coverage, static analysis and general code checking into the LibreOffice development process.

Find out more

• allotropia website
• LibreOffice by CIB
• allotropia on Twitter

LibreOffice is developed by a worldwide community, made up of volunteers, certified developers and companies in the wider ecosystem. Today we’re talking to Caolán McNamara, a long-time LibreOffice developer who works for Red Hat…

Tell us a bit about yourself!

I’m a Principal Engineer at Red Hat, Inc. on the Desktop Team since 2004! And I live on the west coast of Ireland.

What does Red Hat do in the LibreOffice ecosystem?

We try and do a lot of different things, from integration with the GNOME desktop, Calc and UNO work, and porting to architectures such as aarch64 and ppc64le, but I can highlight some of the efforts we make in detecting flaws close to when they get introduced into LibreOffice.

We maintain the regular crashtesting infrastructure, where we import and export 120,000+ documents and typically fix, or identify the triggering commit, any new import/export failures as they are discovered.

Similarly, we maintain the LibreOffice Coverity instance and work to keep the warnings to an effectively zero level in over six million lines of code, as part of that early detection of code flaw process.

In the same theme, we manage the LibreOffice OSS-Fuzz work and work to maintain the level of import related issues to a minimum, especially as a tool to detect potentially security related regressions before they are released, with over 1000 fixed to date.

We recently released LibreOffice 7.3 – what did you work on in that version?

The last user interface feature I did for 7.3 was a little rework of the calc autofilter dropdown, to add “popup on hover” of the color filter submenus and adding color names and some other tweaks, which itself was just an extension of Samuel Mehrbrodt’s (allotropia) more substantial LibreOffice 7.2 work to support color filtering in the autofilter.

Another feature we worked on that landed in upstream 7.3 was extension of the command line conversion of spreadsheets to comma separated value files to additionally support the optional export of each tab of a spreadsheet to a separate output CSV file.

Looking beyond this release, what else are you planning to do?

I’m working on GTK4 version of LibreOffice. It’s not finished by any means, but it’s mostly functional and making progress.

Follow Caolán’s LibreOffice work on his blog, and check out his FOSDEM talk about the GTK4 port.