The Document Foundation Blog


Behind the scenes at TDF: Infrastructure

Filed under: Community, Technology — Florian Effenberger @ 14:10
09.01.15 - 1

LibreOffice admin meeting in Munich, with Alex being the third person from the left

With the beginning of 2015, a new year packed with exciting projects and ideas around LibreOffice and The Document Foundation, we today finish our behind-the-scenes series, to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

I’m Alexander Werner and I am responsible for the infrastructure of The Document Foundation on a contracted basis since March 2014. I have been with the project since its foundation in 2012, and been a longtime supporter of free and open source software. As a volunteer I helped setting up and maintaining our first server and optimizing it to handle the load of the first days.
The infrastructure is one of the most important things The Document Foundation provides for the community. As long as every part is working as expected, it is basically invisible. It is my job to make sure that this is always the case, mostly by orchestrating the different services on our growing number of virtual machines.

When the LibreOffice fork began, we started with only one server where all services were located – mailing lists, both private and public, website, mirror management, wiki and many more. As time went by, this server survived its first slashdot, but soon it became clear that more power was needed. So our infrastructure started growing organically as more and more servers were added. Our admins specialized on different parts of the infrastructure, while the whole configuration was centrally documented in a single ODT file.

It soon became clear that this was not a viable solution – our quest for infra 2.0, as we internally call it, began. The admin team worked under fast escalating load while looking for ways to optimize resource usage, inclusion of new volunteers, configuration documentation and management. Also high availablility of services became increasingly important. In our sparse free time we started creating concepts, tested HA with DRBD, Pacemaker and Heartbeat, evaluated different solutions for centralized documentation and started using tools for centralized configuration management.

It soon became clear that we needed more flexibility for working HA with the solution described above, so as interim solution we started virtualizing services first in paravirtualized guests with LXC and then switched to fully virtualized guests with KVM. For infrastructure documentation I suggested to use the documentation generator Sphinx. The source files for the documentation – human readable RST text files – are located in a git repository, and the online documentation is automatically updated on every push. For configuration management and deployment, I eventually stumbled upon SaltStack.

My daily work consists of working on various small recurring tasks such as helping people with mailing list troubles, adding and removing mirrors in MirrorBrain, installing updates and doing necessary reboots as well as handling unexpected incidents such as the Heartbleed bug.

In spring I started working on our Salt states, made them more reliable and made sure that all user accounts are now managed by Salt. I have setup a new virtualization host with VMs for Gerrit, Jenkins, Bugzilla and Plone. Apart from that I worked on improving the documentation of our services, looking for undocumented and unused services.

I also worked on our AskBot setup. While having set up the initial AskLibO instance, it was decided to contract Evgeny Fadeev, the primary developer of AskBot, to develop additional features needed by our community, which will then be made available upstream again. Despite that, I also did some changes such as enabling the newly-developed multilanguage support, fixed template bugs and administered the list of moderators.

Except for my ongoing work to improve the Salt states and adding more not yet managed servers to our Salt infrastructure, I also continued to concatenate various documentation sources into our centralized repository.

I also worked on a download counter that will be useful to track all our downloads by language, location, version and operating system.

But the most interesting, time consuming and fascinating part of my work was the planning, testing and setup of our new cluster/cloud infrastructure. As it was decided to virtualize all of our services, I looked for a solution that is easy to manage and maintain but provides powerful tools for easily creating highly available services.

After quite some time of evaluating I decided to go for oVirt – a KVM-based virtualization solution that provides a nice out-of-the-box experience, the simplicity of its setup was worlds apart from other solutions. It is also possible to provide fully high available services with only two nodes by having the management engine run as VM on the platform.

During the time of evaluation I also had contact to hardware suppliers and hosters, and after a good offer from manitu we decided to host our new platform on two large, dedicated servers, each with 256 GB RAM and 64 CPU cores. Until the end of the year, over 20 virtual machines were migrated and a third node was ordered that will be used primarily for crash testing and to increase the stability of the platform even more.

If you are interested in learning more about our infrastructure or helping out, consider subscribing to the website mailing list, where infra calls are announced or write a mail to


The City of Munich joins The Document Foundation Advisory Board

Filed under: Advisory Board, Announcements — Tags: , , , — italovignoli @ 10:30

Berlin, January 12, 2015 – The Document Foundation (TDF) announces that the city of Munich has joined TDF Advisory Board, where it will be represented by Florian Haftmann. Back in 2003, the city of Munich – the third largest in Germany – has launched Project LiMux to migrate their software systems from closed-source, proprietary products to free and open-source software. The project was successfully completed in late 2013, which involved migrating 16,000 personal computers and laptops of public employees to free and open-source software. The City of Munich has hosted a LibreOffice HackFest since 2011, to improve features targeted to enterprise environments.

“The city of Munich is a healthy reference for every migration to free software, and as such will add a significant value to our Advisory Board, where it will seat side by side with MIMO, representing the migration to LibreOffice of French Ministries, and with other companies providing value added services on top of LibreOffice,” says Thorsten Behrens, Chairman of The Document Foundation. “Florian Haftmann will be introduced to other members of TDF Advisory Board during next planned meeting, on January 15, 2015.”

TDF Advisory Board has 17 members: AMD, CIB Software, City of Munich, CloudOn, Collabora, FrODeV (Freies Office Deutschland), FSF (Free Software Foundation), Google, Intel, ITOMIG, KACST (King Abdulaziz City of Science and Technology of Saudi Arabia), Lanedo, MIMO (Consortium of French Ministries), RedHat, SPI (Software in the Public Interest), Studio Storti and SUSE.

About the City of Munich and Project LiMux

Munich, Bavaria’s capital, between 2005 and 2013 has successfully managed to migrate around 16,000 PCs in 11 business units and 4 municipal undertakings to an open source based, standard and stable operating system. Munich is the largest public-sector open source stake holder in Germany, and Project LiMux has always had a high visibility.

Project LiMux has been able to reduce in a significant way the dependence from legacy proprietary software products, and attain – in the long term – the desired flexibility of software and architecture, based on three fundamental decisions:

– Introduce a free and open source operating system, with office communications based on open standards for all workstations;

– To acquire or develop platform independent administrative procedures;

– To use a standardised IT platform with consolidated applications and databases.

In such a scenario, a suitable desktop office suite is a strategic core product. In the beginning, LiMux has started to deploy, but by now the reference office suite is LibreOffice.


Behind the scenes at TDF: Executive Director

Filed under: Community, employees, Foundation — Florian Effenberger @ 11:23

With the beginning of 2015, a new year packed with exciting projects and ideas around LibreOffice and The Document Foundation, we continue our behind-the-scenes series, to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

I’m Florian, and I live in the very southern part of Bavaria in Germany, 100 km southwest of Munich, near the border to Austria and Switzerland – a beautiful place to be. ;-)

Today, I’d like to shed a light on my role as Executive Director, a fulltime position which I have held since last March. With TDF having grown over the past years in terms of contributions, projects, ideas, staff and donations, my role as Executive Director is, in a nutshell, to keep everything together and have “the show running”, working for the Board of Directors and with the Membership Committee,floeff2012_400x400 and all the other wonderful volunteers, contributors and staff members like Sophie, Italo, Christian, Robinson and Alex.

Having worked intensively on the statutes and the initial setup of TDF, the first part of my role is taking care of many administrative, legal and tax bits, removing that burden from the board to give them more time for strategy and other items. This work reaches from working closely with our accountant, tax advisor, payroll provider and legal counsel, to dealing with trademark requests, protection of domain names, checking and payment of invoices, and reviewing contracts and insurances, making proposals for the investment of our capital stock and other funds, and of course answering questions on details of the statutes and other parameters of the German “Stiftung”.

The second part of my role is handling the daily operations, which includes replying to and distribution of all sorts of inquiries and requests, be it formal letters, user inquiries and, together with other TDF spokespeople, a variety of press and media inquiries. The daily operations also involve monitoring the budget, organizing our internal file storage, preparing presentations for the annual board meetings, participating in and proposing agenda items for the biweekly phone conferences, handling our donation mechanisms, bank accounts and donation confirmations, monitoring deadlines and working on relations to our Advisory Board. When a new Board of Directors or Membership Committee is elected, or we have new staff members, I have the honour of introducing them to our internal workflow and our entity.

The most exciting part of my job surely is working with our staff in various projects, and the coordination of tasks, deadlines, priorities. As Executive Director, I am responsible for oversight of all budget items and projects TDF is carrying out. At the end of 2013 we have switched to Redmine for project management – started out of the infrastructure team’s needs, it has become an important tool for task and project handling in some non-development parts of LibreOffice. In addition to that, we are running weekly team calls with our staff members, have slots reserved for weekly one-on-one calls, and meet in IRC regularly to discuss current projects and challenges. Every once in a while we also have in-person meetings, mostly during LibreOffice Conferences and FOSDEM. Being responsible for that part of the foundation also involved handling tender processes, job openings and talking to candidates who apply for a job.

We do have a couple of recurring projects, like gradually improving our AskBot instance or writing our formal annual report, but there’s also individual items, like the certification program, the Android tender and the Bugzilla migration.

Should I find some spare time during the weekends, I also like hacking around on our infrastructure, especially our e-mail system and our Redmine instance, and try to join our admin phone calls and infra in-person meetings when possible. Having been a part of the German community for many years, I also try to regularly organize community meetings and phone conferences.

Last but not least, every once in a while I give a presentation, staff a booth at an event, and sometimes I even make it to a magazine or try to say some wise words in a podcast or a lecture. ;-)


Behind the scenes at TDF: Release Engineering

Filed under: Development, employees — Florian Effenberger @ 09:01

Towards the end of the year, The Document Foundation would like to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

Hi, I’m Christian Lohmaier and I’m Release Engineer as well as Infrastructure Administrator at The Document Foundation and have been with the project since it’s foundation. Also long before I was active in the predecessor project, where I filed my first bugreport more than 14 years ago (2000-10-23) and later was one of the founding members of the German native-lang project :-)

cloph_headIn 2014 we redesigned our main user-facing website ( – working with Eleonora Anzini (who created the design) to bring her vision to our CMS (Silverstripe) was one of the first big tasks this year, that already started in 2013 and after lots of tweaking of both the content (managed by Charles-H. Schulz) and the styles/the framework, the new design went live in March.

Release-wise, the year started with 4.1.5 rc1 and 4.2.0 rc3 – only the first in a series of around 50 released builds (betas and release candidates) for QA and curious individuals, not counting the daily/nightly builds provided by our tinderboxes for all platforms.

Maintaining two concurrent release branches at a time, combined with our time-based release schedule ensures a constant flow of bugfixes and updated translations (for the enduser every four to five weeks) with a new major release every six months, but of course also sometimes it is challenging for some parts of the projects.

Especially for each new major (in this context a new x.y.0 release), work starts much earlier, and integrating the translations takes more time than for a bugfix release, on top of that we updated our baseline build configuration a couple of times. From Windows Server 2008R2 with Visual Studio 2010 for 4.1.x and earlier, to Windows Server 2012R2 with Visual Studio 2012 for 4.2.x and 4.4.x to Windows Server 2012R2 with Visual Studio 2013 for master/4.5.x and later, for Linux from CentOS 5 with gcc4.4 for 4.3.x and earlier, to CentOS 5 with gcc4.8/devtools2 for 4.4.x and later and on Mac from 10.6 baseline for 4.3.x and earlier to 10.8/64bit for 4.4.x and master.

As Sophie mentioned in her posting, LibreOffice transitioned from using static dialogs to dynamically created ones (using glade to define them). That, together with other cleanup, did result in many changes in parts of strings that aren’t meant to be translated, but would still result in the string being flagged as new and thus translators would have to retranslate it. To minimize the impact, I used some scripting-foo that can map the old to the new string and thus can reapply translations while automatically updating the non-visible part, hopefully saving the ~120 language teams quite a bit of work.

To reduce translators’ workload before a new major release, we’re going to add a master based translation project in Pootle – this will allow translators to update and polish translations in the whole six months between releases, and not just in the couple of weeks after branch-off. This also allows to sync translations with the master branch, meaning translators can see their translations in a developer build much easier (and thus earlier).

Besides LibreOffice itself, 2014 also the rewrite of the LibreOffice Impress Remote for Android and iOS were released, allowing you to use your smartphone or tablet to navigate between slides and control a virtual laser-pointer.

In the second half of the year, I prepared a Hackfest-VM for the first time (a ready-to-start-hacking VM with prebuilt LibreOffice source tree run on amazon’s EC2) that attendees could use to start coding right away without having to wait 6 hours for their laptops to complete a build. This was later extended to also allow for bibisecting. Unfortunately communication on the location was lacking sometimes, so people didn’t always know how to make use of that goodness, still it’s something that we’ll continue to provide for future hackfests as well (lession learned!).

Also in the second half of the year, the multilang planet was born. It doesn’t only aggregate English blogposts, but blogpostings from contributors in all kinds of languages. If you want to have your blog added, feel free to send a pointer.

The last months of the year were dominated by the migration to a new infrastructure, but you’ll read more about that in another post :-)


Behind the scenes at TDF: Certification

Filed under: Certification, employees, Interviews, LibreOffice — Florian Effenberger @ 10:13

Towards the end of the year, The Document Foundation would like to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

italo-speakingItalo Vignoli, who is in charge of the LibreOffice Certification Program, summarizes the efforts undergone so far, the status quo and the plans for 2015:

Certification Project, looking forward to the first peer-to-peer reviews

certinfographicsTDF has announced the Certification Program in early November, with applications open only to TDF Members until April 2015, for Migrations and Trainings. The first peer-to-peer review session will be at FOSDEM in Brussels, on January 31 and February 2, 2015.

Although the website and all documents are in English, peer-to-peer reviews will be managed – as far as possible – in the native language of the candidate.

For people not able to reach Brussels, we will organize peer-to-peer reviews via videoconferencing.

The deadline for applications, to reach the first review session, is January 16, 2015, to allow two full weeks before the actual peer-to-peer review. In fact, we have to look at applications, approve or reject them (or keep them on hold when they are from non TDF Members), and provide a feedback.

We have a dozen applications so far, from TDF Members, from non TDF Members, and from developers.

We will complete the review of the first applications and provide a feedback by December 23, 2014. The process is still in the early stage, so we are getting up to speed and sharing all the decisions with the group to reach a consensus.

In general, we will accept or reject applications from TDF Members, we will postpone to March/April 2015 applications from non TDF Members, and we will forward applications from developers to the ESC.

In fact, Developers Certification is managed by the ESC, and is by invitation (as reiterated on the website, and on Certification Q&A). So, developers should not apply via the website.

Applying for LibreOffice Certification is not difficult, but to make it even easier we have created an infographics to explain it in detail. Following the seven steps, it will be easier to provide all necessary informations.
For any additional information, please write to


Behind the scenes at TDF: L10N and NLP

Filed under: Community, employees, Foundation, Interviews, LibreOffice — Florian Effenberger @ 10:55

Towards the end of the year, The Document Foundation would like to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

Sophie Gautier is in charge of our L10N and NLP projects at The Document Foundation, and gives you insight into this key part of our project:

_SDS5526L10n – NLPs status quo

I would like to give a brief overview of the many things that happened or are in the pipe either on the Localization project (L10n) or on the Native Language projects (NLPs). For the latter, it is not always easy to know what is going on locally, but we tend to get more and more feedback from these groups which is really great.

So, on the Localization side, several new languages were added to Pootle these last months, more Indic languages, for example. Translating UI and Help is a very huge task, and when you think it is finished, there is still some work to do for the next version. For example, currently, the teams are in the starting blocks to translate the 4.4.x new features strings and the various enhancements that have been provided by the Design team. Also the change of file format to .ui means that the l10n teams had to translate again all the dialogs. Fortunately, this change is of great help because the dialogs adapt to the length of the strings (no need anymore to count the characters in the word to fit the space), but we are also able to display those dialogs in Glade, allowing to see the strings in context, which is something all localizers are dreaming of! All in all, that makes many new words for both UI and Help projects. And this is not the only translation projects we handle via Pootle, there is also the Website, Impress for Android and iOS, sometimes AskBot projects.

Dedicated to newcomers of the l10n project, two guides have been written; one concerning how to use Pootle, the second one on the structure of .po files (for example, it shows how to distinguish variables or which xml tags are used). There was absolutely no documentation on the structure contents by the past and one had to guess what he had to translate or not. And it is very easy to break a build when tags miss or mismatch, so this brings some relief to the developers too.

Thanks to our Brazilian friends several of the help articles concerning new functions have been completed. We are also working on porting the translation of the help files on the wiki. This is a difficult task because we do not want to complicate the translation task on one hand, but we want to simplify the help maintenance and open it to non-technical contributors on the other hand, which is currently impossible. Some technical issues have still to be resolved, but we are optimistic that we will be able to set it in a near future. As a work in progress also, we hope to push the migration to a new version of Pootle, with an integrated translation memory.

On the Native Language projects side, we are happy to see more and more contributors to the local projects and really good news coming from several of them, like the Italian community or the Japanese and Chinese ones. They not only contribute to their local projects, but you can find those members active in QA, development or documentation.

One of the major tasks handled this year by these teams was the translation and adaptation of the new website design. During the year, the website itself was translated on Pootle and the content by website owners. This gives a uniformed design to all the language sites bringing more quality and a professional look and feel to our project.

One way to measure the growth of activities in these projects is how we all together manage the press releases. Once the text is fixed by the marketing project, the native language projects translate them and send them back to the marketing team for distribution to the press in their countries. We are now able to release in almost 9 languages for each major release. It is also something really exciting to see how the developers, the quality assurance, native language, design and marketing projects interact during the last month before the release. Of course it happens also all time between two or three of them, but the communication has improved between all of them.

Another great thing that has happened recently while in heavy discussion since some times, is the Planet in all languages. It is really impressive to see all those languages mixed in one thread but that you can filter by the language you prefer. There is currently ten languages available covering several blog writers.

Always trying to be as transparent as possible and to bring as much information to the community as we can, the Annual Report due as a TDF official document to the Berlin authorities, has been translated into English and is available to the Native Language projects for their own use, to inform either on the product and the community.

On the local side, TDF has supported several hackfests and numerous events have been organized all over the world by the Native Language Projects. And we are really happy that the Danish team is organizing the next international LibreOffice conference in Aarhus.

To reflect all this effervescence, we have set a Big Thank You page on the wiki, where all L10n and NLPs contributors are invited to add their name. But that’s not all, we have also a world map, detailing the skills of the contributor in addition to his location. And stay tuned, more is coming!

Create a Template for LibreOffice, and get a free T-shirt

Filed under: Announcements, LibreOffice, Technology — Tags: , — italovignoli @ 09:43

The Document Foundation launches a competition to increase the number of document templates bundled with the upcoming major release of Libreoffice, open to designers, artists, and creatively talented users.

Deadline for submission, to be included in LibreOffice 4.4, is January 4, 2015. Templates submitted after this deadline will be considered for later LibreOffice major and minor releases, like LibreOffice 4.5 or LibreOffice 4.4.1.

Templates will be selected by the members of the LibreOffice Design Team, and may be edited before the inclusion. Authors of the templates bundled with LibreOffice 4.4 will get a free T-shirt either at LibreOffice booth at FOSDEM on Saturday January 31, or Sunday February 1, 2015, or by post after FOSDEM, and will be credited with a mention on They will also have a chance to meet LibreOffice developers and the design team during and after the show.

To be considered for inclusion, templates must meet the following conditions:

  • They are an original work, and are not converted from existing templates.
  • They are licensed under Creative Commons CC0.
  • They are based only on fonts bundled with LibreOffice (Caladea, Carlito, DejaVu, Gentium, Liberation, Libertine G, Open Sans, PT Serif, Source Code, Source Sans).
  • They are based on LibreOffice styles, and not on direct element formatting. Styles must be created according to the expected use of the template.
  • They contain only a minimum of text (ideally, no text at all), as they will not be translated for LibreOffice 4.4. Because of that, language must be en_us.

To participate, either upload the template on TDF wiki or send it by email to, and we will add it to the list. Templates will be collected here:

Please specify the category and/or the intended use of the template, and the license of the template. You can send any number of templates, provided that all of them meet the above conditions.

For more information about creating templates, please check here: and

As an example, categories of templates could be: books of various types, address/phone books, business cards, calendars, curriculum vitae/resumes, essays, expense reports, letters, lists, records and reports of various types, schedules, etc.

Be creative ! We look forward to bundle your template designs !


Behind the scenes at TDF: Quality Assurance (QA)

Filed under: Community, employees, Interviews, LibreOffice, QA — Florian Effenberger @ 18:30

Towards the end of the year, The Document Foundation would like to share achievements in 2014 with our community and our generous donours, to whom we’d like to express our sincerest gratitude and thanks for their incredible and wonderful support and their invaluable contributions!

As a start, Robinson Tryon, who is in charge of Quality Assurance (QA) since August, and summarizes the efforts in this important area:robinson-in-brussels

Hi all,

I’m Robinson Tryon and I’m a QA Engineer for The Document Foundation. I became quite interested in computers in high school and got my first taste of Free Software playing around with RedHat Linux on a spare machine.

In college I started to study computer science in earnest, and found myself very interested in the topics of human-computer interaction and computing freedom. I can’t remember who first introduced me to the Free Software Foundation, but I have fond memories from my undergraduate years of attending annual membership meetings at MIT and thinking of how I’d like to get a job where I could spend my time working on Free Software.

In the years since I graduated with a degree in computer science, I’ve been fortunate to be able to work with a number of different organizations and labs on Free Software projects. I’ve worked on a multimedia engine used to create training simulations for doctors and first-responders, tools for teaching non-technical people how to use programs such as git and ssh, and a series of web-based games designed to help libraries, museums, and other organizations crowd-source metadata for images and video in their collections. I was very excited to join the Document Foundation this year and bring my experience to the LibreOffice project.

My first contributions to LibreOffice came early-on in 2010 when the project was just starting out. The renewed energy and community-focus espoused by the leaders heartened me, and the reduced barriers to contribution sounded very promising. I tested out new builds and made a few small edits to the wiki, but didn’t get seriously involved until a couple of years later. Up until that point, I was just a user.

When I was still in college, I remember running Sun’s off of a Knoppix LiveCD. I desperately wanted to find an alternative to running MS-Office to type up all of my papers and reports, and just using a text editor wasn’t quite cutting it. Although I wasn’t always able to work on my own desktop computer in my dorm room, carrying around a Knoppix CD made it possible for me to boot-up and run a Free Software office suite on the public cluster machines.

By the time LibreOffice had its first release, I had upgraded from the CD and could carry around Free Software programs on a USB stick, ready to be run on any computer. I currently carry a USB stick with builds of LibreOffice for Windows, GNU/Linux, and Mac. My thinking is that if a friend ever needs a hand opening documents on a computer, it’d be great for me to have the right tool ready to go for them. In fact, using LibreOffice to help out a friend is what got me very involved with LibreOffice and the QA Team.

A friend of mine had a large number of documents in proprietary formats (word processing, spreadsheet, etc..) and reading through the LibreOffice documentation I found out that the suite has some excellent tools for conversion of documents from one format to another, including the ability to bulk-convert via the command line one hundred documents as easily as one document. While I was doing my research, I started to chat with contributors to the LibreOffice project, I attended a couple of QA Meetings, and before I knew it was an active member of the QA Team!

When I first started out contributing to LibreOffice, I focused on some basic bug triage tasks and filled-in missing pages on the TDF wiki. As my understanding of the project and its members grew, I was able to make contributions to Bugzilla, to the BSA, and MediaWiki, and was able to help set up tools such as ownCloud. I currently work on a large number of different QA tasks for LibreOffice, including generating binary-bisection or “bibisect” repositories, improving and updating QA documentation on the TDF wiki, and overseeing the implementation of improvements to Bugzilla. Right now I’m gaining experience as a Release Engineer for LibreOffice.

In addition to the technical tasks I undertake for LibreOffice, I work on LibreOffice outreach — both in the US and abroad. Although we have a large number of active users, only a small fraction of them are active contributors. We are always looking to expand the number of contributors in each of our teams, and are excited about getting more people involved in QA through our BugHunting sessions and LibreFests.

A LibreFest is usually a one or two-day event in which various LibreOffice teams may participate. LibreFests, just like hackfests, are typically held in person, as that’s the best way for us to collaborate with and teach new contributors. When the QA Team participates in a LibreFest, users are asked to perform basic or advanced bug triage, to bibisect regressions, and to file new bugs that they observe. With experienced LibreOffice team members present, users feel much more comfortable stepping outside their comfort zone and taking on QA tasks that they wouldn’t try to tackle by themselves.

In our BugHunting sessions, we spend a weekend (usually Fri-Sun) testing the latest builds of a new Release Branch. One of the tools we use to test the builds is MozTrap — a test case management system that help to ensure greater reliability and consistency. Through extensive use of LibreOffice, we hope to shake-out any obvious bugs and squash them before going further in with the release process.

Speaking of BugHunting sessions, this weekend (Dec 19-21), we’ll be having a BugHunting session for the upcoming 4.4 Release Branch. We’ve worked to make it easy for newcomers to participate. To join in, or just for more information, see:

LibreOffice 4.4.0 bug hunting sessionIf you’re looking for a way to participate in LibreOffice, or just curious about what we do in QA, please stop by our mailing list or our IRC channel. There’s so much more that we do that can’t be contained in a single blog post, and we’d love to tell you all about it!


The Document Foundation announces LibreOffice 4.3.5

Filed under: Announcements, LibreOffice — italovignoli @ 14:00

Coverity Scan Project LibreOffice OverviewBerlin, December 18, 2014 – The Document Foundation announces LibreOffice 4.3.5, the fifth minor release of LibreOffice 4.3 “fresh” family, which is a stable release of the more advanced version of the software, targeted to individual and enterprise users. LibreOffice 4.3.5 contains over 70 bug fixes.

The Document Foundation suggests to deploy LibreOffice 4.3.5 in enterprises and large organizations when backed by professional support by certified individuals (a list is available at capable of providing value added support.

People interested in technical details can find change logs for LibreOffice 4.3.5 here: (fixed in RC1) and (fixed in RC2).

The image on the left provides the updates figures about LibreOffice source code as provided by the Coverity Scan Service on December 14, 2014. To learn about LibreOffice and Coverity Scan, you can read this blog post.

Download LibreOffice

LibreOffice 4.3.5 “Fresh” and LibreOffice 4.2.8 “Still” are immediately available for download from the following link:

LibreOffice users, free software advocates and community members can support The Document Foundation with a donation at


TDF announces the second and final LibreOffice 4.4 bug hunting session from December 19 to December 21

Filed under: Announcements, QA — italovignoli @ 18:07

The Document Foundation (TDF) announces the second LibreOffice 4.4 bug hunting session, which will happen from December 19 to December 21, 2014, immediately after the availability of the first release candidate of the new major release (with the final release planned for the end of January 2015).

Details of the second LibreOffice 4.4 bug hunting session are available on TDF wiki at A list of LibreOffice 4.4 features that have to be checked for bugs and regressions is also on TDF wiki:

To participate, it will be necessary to download LibreOffice 4.4 RC1 for Windows, MacOS or Linux from Filing bugs will be extremely easy, thanks to the help of experienced volunteers who will be around on the QA mailing list ( and IRC channel (irc://

« Newer PostsOlder Posts »

The Shocking Blue Green Theme. Blog at


Get every new post delivered to your Inbox.

Join 3,587 other followers

%d bloggers like this: