Home » Archives for Mike Saunders » Page 127

Author: Mike Saunders

LibreOffice 6.0: The stats so far

On January 31, we released LibreOffice 6.0 (shortly followed up by 6.0.1). So what has happened in the last two weeks? Let’s look at some statistics…

969,108 downloads

Yes, there have been almost 1 million downloads of LibreOffice 6.0 since release day. Of course, this is just part of the overall downloads of LibreOffice – we also offer the “still” 5.4 family, which has reached version 5.4.5 and is more suited to enterprise deployments.

661,539 visits to our website

Our main website is the central resource for all things LibreOffice, including downloads, release notes, help, community support and more.

252,495 visits to our blog

Most of these were for the release announcement, but we’ve been posting other updates as well. On a related note, if you want to follow blog posts by other members of the LibreOffice community, check out the TDF Planet.

Over 3,500 donations

Donations are the lifeblood of The Document Foundation: they help us to support the LibreOffice project with infrastructure, events and a small team working on release management, quality assurance (QA), marketing, design and documentation. Click here to see how we used donations in 2016 – and see this page if you’d like to support us too. A huge thanks to everyone who donated!

80,516 views of our New Features video

As with previous releases, for LibreOffice 6.0 we made a video showcasing some of the great new features. (And on the topic of videos, we’ve just uploaded talks and presentations from the LibreOffice community at FOSDEM, Europe’s biggest free software developer meetup – click here for the playlist.)

87,358 impressions of the announcement tweet

We use Twitter to spread the word about LibreOffice, free software and open standards, and thanks to our supporters who retweeted the announcement, over 87,000 people saw it. It also had 561 retweets and 621 likes.

32,578 people reached on Facebook

Another social media platform we use is Facebook, where our page has 51,987 likes. In addition, we’re active on Google+ where we have 16,731 followers, and our announcement of LibreOffice 6.0 received 217 +1s.

So that’s an overview of activity in the last two weeks – but there’s much more going on in the LibreOffice project! If you’d like to get involved with a friendly community that’s passionate about open source and open standards, you can help us in many ways – see this page to get started.

And thanks to everyone in the community who helped to make LibreOffice 6.0 happen!

LibreOffice talks and presentations at FOSDEM 2018

FOSDEM is a major event in the free and open source software world – thousands of FOSS supporters get together to discuss new features, work on bugs, make new contacts, and just have a great time.

This year, many members of the LibreOffice community were there too, and gave talks and presentations in the Open Document Editors devroom. We’ve added the videos to a playlist, embedded below, so enjoy browsing through them to see what’s to come in LibreOffice! (Click the button in the top-left to switch between videos in the playlist.)

Please confirm that you want to play a YouTube video. By accepting, you will be accessing content from YouTube, a service provided by an external third party.

YouTube privacy policy

If you accept this notice, your choice will be saved and the page will refresh.

LibreOffice community focus: Development

Over the past few weeks, we’ve talked to the documentation, localisation, QA (quality assurance) and design communities about their preparations for LibreOffice 6.0, which is due to be released this week. For our final Community Focus, we turn to the developer community, which has helped to implement many of the new features you can see in the release notes.

How does the community work on new features?

Development in LibreOffice is achieved using a wide variety of tools and services, which is a testament to the maturity and longevity of the project. The LibreOffice developer toolkit is best summarized by going through the lifespan of a single patch:

1. Communication. When a user would like to see a new feature in LibreOffice, or identifies a problem, he/she has one of several options to bring it up:

  • Bugzilla: We use our own self-hosted Bugzilla instance. This one of the biggest installations of Bugzilla out there. If you don’t want to report a new issue but would like to contribute towards existing ones, we collect and sort bugs based on skill, difficulty and topic. We also provide a list of EasyHacks that new contributors are encouraged to tackle for a start.
  • E-mail lists: We have several e-mail lists used for general discussion, reports, help and development, the two most important are: libreoffice@lists.freedesktop.org (developers) and users@global.libreoffice.org (users). Here’s how to sign up to the lists.
  • IRC: Core and not-so-core LibreOffice hackers usually hang around in the #libreoffice and #libreoffice-dev channels on the Freenode IRC network. You are welcome to join and ask for help, guidance and general support in there.
  • Telegram, QA, Twitter, etc: We are present on many other online services – global or localized for your community. Check the full list here.

Users, developers and project members usually roam these communication channels and both development and general discussion is taking place. Communication is key. Then the next part is…

2. Development. During this phase the most important tools in the LibreOffice developers’ toolkit are:

  • Git: The LibreOffice source code is self-hosted using Git and is available here. Getting started with LibreOffice and Git is outlined on this page, and an easy build set-up can be achieved using the logerrit tool that we provide.
  • Wiki: The Wiki is a good place to look for information and refine your question before reaching out.
  • Code search: You can easily search (grok) the codebase and reference parts of code in your inquiries to developers using the Opengrok installation.

3. Next steps. Once general agreement has been achieved on how to implement a new feature or fix a specific bug, the following services are used:

  • Gerrit: Core developers and newcomers alike collaborate on the shared code base, using the communication channels outlined before, and Gerrit code review. The Gerrit procedure is recommended for all submissions and all projects that are part of the LibreOffice realm. Signing up on our self hosted Gerrit is crucial to the development process and getting you code admitted into the project.
  • Jenkins and Tinderboxes: Once a specific patch is submitted via Gerrit, a set of automatic continuous integration QA&build tests are being run for all supported platforms, and any defects or regressions will be reported automagically along with feedback from other developers.

An overview of our most critical infrastructure used for development and release engineering is available on this site, while the Wiki has a list of additional services.

Another useful tool – a new addition to the toolkit – is the LibreOffice dashboard. You can use it to inspect the development, release and lifecycle of LibreOffice core and its associated repos with a bird’s-eye view.

So that’s the final Community Focus – a big thanks to all developers and testers who’ve helped to add the many great new features in LibreOffice 6.0! (And thanks to Teodor Mircea Ionita for his help with this post.) Stay tuned to this blog for the official announcement of the new release…

Extended: Job Search for a Development Mentor (#201711-01)

We originally posted this in November, but we are now extending the deadline for applications to February 16, 2018. Note that we will be at FOSDEM (building K, level 1, group A) on February 3 and 4, so you can talk to us in person there!

The Document Foundation (TDF), the charitable entity behind the world’s leading free office suite LibreOffice, seeks an individual – or individuals part (or full) time – to be

a Development Mentor

to start work as soon as possible. The role requires the following:

  • Self-starting, remote working experience
  • Experience contributing to FLOSS communities
  • Excellent communication skills, with enthusiasm for mentoring
  • Coding experience (LibreOffice coding preferred)
  • Willingness to travel to Hackfests & conferences in Europe and globally

The role involves working from home at your location for at least 20 hours per week, up to full-time and includes among other items:

Supporting existing mentors in the LibreOffice community including:

  • Building relationships between existing mentors and new contributors
  • Identifying and on-boarding new contributors
  • Affirming and encouraging their contribution
  • Building initial relationships with them
  • Encouraging them to join IRC to meet the teams
  • Introducing them to domain experts for deeper learning
  • Helping to educate new contributors by
  • Positively reviewing their code contributions
  • Introducing them to our tooling and culture
  • Attracting new contributors by promoting the project
  • Interaction with UX volunteers

Previous experience with such tasks is highly welcome, so is using free software. Speaking and writing English reasonably well is a mandatory requirement.

The work time during the day is flexible, apart from some fixed times when availability is required (e.g. during meetings, which usually take place at 14:00 or 15:00 UTC once per week).

TDF welcomes applications from all suitably qualified persons regardless of their race, sex, disability, religion/belief, sexual orientation or age.

As always, TDF will give some preference to individuals who have previously shown a commitment to TDF, including but not limited to members of TDF. Not being a member, or never having contributed before, does not exclude any applicants from consideration.

TDF is looking forward to receiving your applications, including curriculum vitae, your financial expectations, and the earliest date of your availability, via e-mail to Florian Effenberger at floeff@documentfoundation.org no later than February 16, 2018. You can encrypt your message via PGP/GnuPG.

If you haven’t received feedback by March 16, 2018, your application could not be considered.

LibreOffice community focus: Design

LibreOffice’s design community works on the software’s user interface (UI), improving its usability and accessibility. With LibreOffice 6.0 due to be released at the end of the month, we talked to members of the community to get their perspectives on the new version…

What have you been working on in preparation for LibreOffice 6.0?

Various things, including:

  • New table styles and new gradients (click for bigger):

  • The LibreOffice 6.0 motif/splash screen:

  • And menu and toolbar improvements

What are your favourite new features in this release?

Both GSoC (Google Summer of Code) projects are really nice: the revamped customization dialog, and the special character dialog with quick access from the toolbar. In addition, there’s the ability to rotate images to arbitrary degrees, and many other small improvements.

What tools and services do you use in the design community?

At the moment we use Balsamiq Mockups, but next we switch to Pencil. In addition, we use LibreOffice Draw (eg for the new motif) and Inkscape. For communication, we are active on IRC in the #libreoffice-design channel and Telegram.

Finally, how can people get involved with the design community?

A big thanks to the design team for their input and improvements in LibreOffice 6.0. For our final Community Focus, we’ll talk to the development community – more on that soon!

LibreOffice community focus: QA (quality assurance)

With LibreOffice 6.0 due to be released at the end of the month, we’ve been talking to various communities involved in the project. In the last couple of weeks, we’ve chatted with the localisation and documentation teams, and today it’s the turn of QA (quality assurance), which is coordinated by Xisco Fauli…

What has the QA community been working on in preparation for LibreOffice 6.0?

During the development of LibreOffice 6.0, three Bug Hunting Sessions were held (6.0 Alpha1, 6.0 Beta1 and RC1), the last one just two weeks ago. There was also a parallel event organized by Muhammet Kara in Ankara, where volunteers gathered to test LibreOffice 6.0 RC1. Besides that, the QA team is constantly testing the latest daily builds, testing new features, and triaging the bugs reported on Bugzilla.

What are your favourite new features in this release?

That’s a difficult question, especially taking into account all the improvements done in this release to LibreOffice Android Viewer, to LibreOffice Online or the work done by the Google Summer of Code students among others. But if I had to choose one, I think I’d go for the characters dialog refactoring done by Akshay Deep and the UX (user experience) team, as this is probably the feature I will use the most in the near future. Here’s how it looks:

What tools and services do you use in the QA community?

A very handy tool recently completed by Markus Mohrhard is the automated updater for Windows and Linux, which allows the QA team to test daily builds without having to manually download the latest build every time.

This is very practical as testers no longer need to worry about constantly updating to the latest build, and can focus more on testing the program instead, assured that they are testing changes done to the code just the day before.

This tool was presented at the beginning of the LibreOffice 6.0 development cycle, and I believe it will have a very positive impact on the quality of 6.0 as it shortens the time between a problem being introduced in the code, and the time it’s found.

Another tool we’ve been using for some time now is the bibisect repositories, which allow us to find the exact code commit where a bug was introduced, increasing the chances that the bug gets fixed and reducing the time until it gets fixed.

Another tool which is fulling working now is a set of scripts called office-interoperability-tools that we use to automatically find document layout regressions in the master code branch compared to other office suites (in our case we use MS Office). Right now we use it with 8,450 files, and I believe it will also have a positive impact on the quality of LibreOffice 6.0.

Finally, it’s important to mention the main tool used in QA, Bugzilla, the place where all bugs are reported and triaged. Then there’s the wiki page where the QA documentation can be found, and testlink, the application to manage manual tests.

Finally, how can people get involved with the QA community?

The’re many ways one can help LibreOffice QA. Probably the simplest one would be: download the latest pre-release build (LibreOffice 6.0 RC2 as of today), install it and use it as you would use LibreOffice in your daily basis (but take into account it’s still a pre-release, so it’s not recommended to use it with important documents). If you find anything working incorrectly, please report it to Bugzilla.

On the other hand, if you prefer to follow a set of manual tests, you can use testlink (see the documentation for that. We also need help to triage bugs that are not-yet-confirmed, or retest old bugs to see if they might have been fixed.

Lastly, if you’re looking for something especially exciting things to do, you can help us to test daily builds, bisect bugs or write UI-tests. Don’t hesitate to join the #libreoffice-qa channel and say hello. We’ll be grateful to help you with any question or problem you have!

Much gratitude to Xisco and the diligent QA community for helping to make LibreOffice 6.0 a solid release. Their efforts are appreciated by users across the world. Next up, we talk to the design and development communities – more on this blog very soon…

Press Releases

Announcement of LibreOffice 25.8.4

Berlin, 18 December 2025 – LibreOffice 25.8.4, the fourth minor update to the free office suite developed by volunteers for…

Open Document Format

The Role of ODF in the Era of Digital Identity and Authentication

Digital identity has become an integral part of everyday life. We use it to access work tools and sign documents…