LibreOffice leverages Google’s OSS-Fuzz to improve quality of office suite

Berlin, May 23, 2017 – For the last five months, The Document Foundation has made use of OSS-Fuzz, Google’s effort to make open source software more secure and stable, to further improve the quality and reliability of LibreOffice’s source code. Developers have used the continuous and automated fuzzing process, which often catches issues just hours after they appear in the upstream code repository, to solve bugs – and potential security issues – before the next binary release.

LibreOffice is the first free office suite in the marketplace to leverage Google’s OSS-Fuzz. The service, which is associated with other source code scanning tools such as Coverity, has been integrated into LibreOffice’s security processes – under Red Hat’s leadership – to significantly improve the quality of the source code.

According to Coverity Scan’s last report, LibreOffice has an industry leading defect density of 0.01 per 1,000 lines of code (based on 6,357,292 lines of code analyzed on May 15, 2017). “We have been using OSS-Fuzz, like we use Coverity, to catch bugs – some of which may turn into security issues – before the release. So far, we have been able to solve all of the 33 bugs identified by OSS-Fuzz well in advance over the date of disclosure”, says Red Hat’s Caolán McNamara, a senior developer and the leader of the security team at LibreOffice.

Additional information about Google OSS-Fuzz is available on the project’s homepage on GitHub – https://github.com/google/oss-fuzz – and on Google Open Source Blog: (1) https://opensource.googleblog.com/2016/12/announcing-oss-fuzz-continuous-fuzzing.html (announcement), and (2) https://opensource.googleblog.com/2017/05/oss-fuzz-five-months-later-and.html (results after five months).

The Document Foundation announces the MUFFIN, a new tasty user interface concept for LibreOffice

muffinBerlin, December 21, 2016 – The Document Foundation announces the MUFFIN, a new tasty user interface concept for LibreOffice, based on the joint efforts of the development and the design teams, supported by the marketing team. MUFFIN is an acronym for My User Friendly & Flexible INterface, and focuses on the three areas suggested by LibreOffice users during the development of the concept:

  1. My: LibreOffice users want a “personal” UI, with different options capable of adapting to the user’s personal habits, and not a single UI without options.

  2. User Friendly: of course, any UI should be as user friendly as possible, but LibreOffice users have clearly asked for a “modular” UI, where they can set their own level of user friendliness, and not a single UI without options.

  3. Flexible: the increasing number of LibreOffice users deploying the software on different hardware platforms (for instance, a desktop and a laptop), each one with different characteristics and screen size and resolution, have asked for a UI that can be tweaked to leverage the screen real estate, and not a single UI without options.

INterface: The MUFFIN concept is the combination of different UI elements, which are going to be available starting from LibreOffice 5.3 either as a standard or experimental feature: the Default UI (with toolbars), a Single Toolbar UI, the Sidebar with a Single Toolbar, and the new Notebookbar (experimental, and not recommended for production use). Each UI layout has been thought to serve a different cluster of LibreOffice users.

LibreOffice Writer with Standard Toolbar
LibreOffice Writer with Single Toolbar
LibreOffice Writer with Sidebar
LibreOffice Writer with Notebookbar

The rationale behind the MUFFIN is further explained in a marketing backgrounder [PDF] and in a specific blog post on TDF Design Blog.

LibreOffice has a new Extensions & Templates website

Berlin, December 14, 2016 – The Document Foundation announces the new Extensions & Templates website, which offers an improved user experience to both developers and end users: https://extensions.libreoffice.org. The resource is now based on the latest version of the Plone open source Content Management System, and has been both coordinated and developed by Andreas Mantke, deputy member of the board at The Document Foundation.

“Two of LibreOffice’s most distinctive characteristics are the possibility of adding features through extensions, and improving quality and consistency of documents thanks to templates”, says Andreas Mantke. “After six years, we decided to refresh the existing resource, to make it easier for developers to upload their files, and for end users to search and download them. I’d love to see an increasing number of contributors uploading extensions and templates”.

extensionsLibreOffice Extensions & Templates website offers 304 extensions, with 678 different releases, and 339 templates, with 376 releases. The three most popular extensions are: “Clipart gallery of danger signs”, “Copy only visible cells” and “LanguageTool”. The three most popular templates are: “Personal Budget Template”, “Simple FAX Template” and “LibreOffice Presentation Templates”. A large number of available resources have been contributed by end users.

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at http://donate.libreoffice.org.

Document Liberation Project: progress so far in 2016

If you haven’t heard of the Document Liberation Project (DLP) before, we made a short video explaining what it does and why it’s important. In summary: it supports development of software libraries to read documents from many (usually proprietary) applications. If you’ve ever opened a file generated by Apple Pages, WordPerfect or Microsoft Works in LibreOffice, you’ve benefitted from the hard work of the DLP team. And DLP libraries are used in many other prominent FOSS tools such as Inkscape and Scribus as well.

For example, here’s a file being created in Apple Pages, and the same file being rendered in LibreOffice thanks to DLP libraries (click for a bigger version):

So, what has been going on in the DLP so far this year? Here’s an overview.

New releases

In January, libetonyek 0.1.6 was released with a bunch of new features. This library, which helps applications to read files produced by Apple Keynote, Pages and Numbers, can now properly parse links, lists and text languages in Keynote 6 files, while resizing of tables is handled properly. Text containing non-ASCII characters (ie, the majority of non-English languages) is now managed much better as well.

Scribus 1.5.1 was released in February, as part of the development process towards a stable 1.6 release of this desktop publishing tool. Along with many new features and updates, Scribus 1.5.1 makes use of the libfreehand 0.1.1 library, which allows it to read documents created in Adobe FreeHand. This feature is still marked as experimental – as it’s very early days – but is already working well and will be very useful to some Scribus users.

March saw the release of two other DLP libraries: libpagemaker 0.0.3 (for parsing Adobe PageMaker documents) can now read big-endian (Mac) files, while writerperfect 0.9.5 (for conversion of various document formats to ODF, EPUB and AbiWord) includes a number of build fixes and can also convert old StarOffice files.

Website updates

In order to make the goals of the Document Liberation Project clear and accessible, and attract potential new contributors, we redesigned the front page of the DLP website. We broke up the big chunks of text that used to dominate the front page, and added logos and links to several projects that use DLP libraries.

Here’s a before-and-after comparison:

In addition, we added a link to the aforementioned video that describes DLP and tries to make it accessible to a wider audience. As more and more computer users recognise the downsides of non-standard file formats and vendor lock-in, projects like the DLP will become increasingly important.

Get involved!

DLP is always looking for new contributors, and appreciates all help with coding, testing and documentation. If you enjoy programming and tackling new challenges, creating a new import library can be especially rewarding! Fathoming out the insides of a closed file format is fascinating, and you’ll get plenty of appreciation from users in the future who can finally open their old documents without struggling to run ancient software in a virtual machine…

So to join, visit the contributor page for pointers to get started.

LibreOffice: Advent Tip #24

Bugzilla Main PageLibreOffice last tip of the series (a huge success, according to the numbers) is slightly different from the previous ones, because is not a real tip but an invitation to help the project by submitting bugs and regressions.

In fact, only with the help of our large user community (stay tuned for the numbers…) we will be able to improve the quality of LibreOffice, release after release.

To file a bug or a regression, there is a specific resource: Bugzilla (the image on the left is a thumbnail of the home page). The process might look difficult for a first time user, but there is a nice tutorial (download PDF) which explains the different steps in detail.

Increasing and improving the number of bugs and regressions filled correctly would be the best gift that users could do to the project in 2016 and beyond.

LibreOffice: Advent Tip #23

zoom

LibreOffice provides a Zoom & View Layout dialog which makes it easier to set the size of the document inside the software window. The feature can be accessed either with the menu View > Zoom > Zoom… or by double clicking on the zooming percentage in the lower right corner. The dialog allows to set both the Zoom Factor and the View Layout, with a number of different option for each choice.