Annual Report 2020: TDF and LibreOffice infrastructure

In 2020, the infrastructure team added new services, implemented a new Extensions and Templates site, and worked on a replacement for Ask LibreOffice

(This is part of The Document Foundation’s Annual Report for 2020 – the full version is here.)

LibreOffice’s infrastructure team is responsible for maintaining the hardware, virtual machines and services that enable the wider community to develop, market, test, localize and improve the software. The public infrastructure is powered by around 50 kernel-based virtual machines (KVMs) spread across four hypervisors, plugged to an internal 10Gbps switch, hosted at Manitu in St. Wendel (Germany), and managed with libvirt and its KVM/QEMU driver. The virtual disk images are typically stored in GlusterFS volumes – distributed across the hypervisors – except for some transient disks (such as cache) where the IOPS requirement is higher and the redundancy less important.

In 2020, the infra team added various new services, such as the new SilverStripe-based Extensions and Templates site. Some background to the technical and design decisions behind the site are here on the blog.

Meanwhile, Discourse was investigated as a likely AskBot replacement, while several VMs for deployment tests outside the scope of infra were handed over (such as decidim). The infra team worked on Moodle (an e-learning platform), build bots, integration of the Weblate translation platform into the TDF development dashboard, and a crashtest box (sponsored by Adfinis).

Along with the new services, there were many notable upgrades too. Some machines are still running Debian GNU/Linux 9 (codename Stretch), but most are now upgraded to Debian 10 (codename Buster). Other updates include: Nextcloud 16 to 20, Gerrit 2.16 to 3.2, LibreOffice Online 6.3 to 7.0, and Mediawiki 1.31 to 1.35. Finally, OpenGrok, Etherpad Lite, Weblate and the Grimoire dashboard received updates too.

Notable refactoring/improvements took place in the online help backend, along with the backends for bibisecting and mailing lists. The team started collecting metrics for download counters and the update checker, and worked on improving IRC bots, the monitoring setup, and a distributed backup solution.

Documentation was improved to make onboarding of new infra team members easier, while the SSO (Single Sign-On authentication) system was expanded with more services: Gerrit, the new extension site, Discourse, Jitsi and Moodle.

Like what we do? Support the LibreOffice project and The Document Foundation – get involved and help our volunteers, or consider making a donation. Thank you!

Get printed copies of LibreOffice handbooks!

LibreOffice’s Documentation Team writes, updates and translates many handbooks. These are full of tips, tricks and tutorials covering the whole office suite. You can find PDF and ODT versions on this page – but sometimes it’s nice to have a hard-copy, printed version, right?

Well, you can get those too! Our community has made these available via the online bookshop Lulu (which was started by Red Hat co-founder Bob Young). These are printed on-demand, in various facilities around the world, and have global shipping.

So, if you want to learn more about LibreOffice but fancy a break from your computer screen, check them out!

Contest for LibreOffice Ecosystem and LibreOffice Technology logo

The Strategic Marketing Plan discussed in 2020 has introduced a couple of concepts – LibreOffice Ecosystem and LibreOffice Technology – which will be the cornerstone of LibreOffice marketing activities for the foreseeable future, and will be deployed on web properties, marketing materials, documents, presentations and merchandise for events. Now, we need high-impact visuals to stress the importance of these concepts for LibreOffice.

Based on the success of the community contest for the 2020 Anniversary Logo, which has provided a consistent visual image for presentations at virtual events in 2020 (and will be used in 2021 as well), The Document Foundation is challenging community members with the task of developing two different logos:

(1) LibreOffice Ecosystem logo, to underline the unique characteristics of the LibreOffice project: global reach, continuous research for improvement and high quality, inclusiveness, loyalty to copyleft licenses, smooth combination of paid and volunteer contributors, and eventually lots of fun especially at events. The LibreOffice Sustainability slide deck provides an extensive description of the concept: https://nextcloud.documentfoundation.org/s/4qLzRad8wNd8pFk.

(2) LibreOffice Technology logo, to underline the uniqueness of the LibreOffice platform, which provides a single common engine for all platforms, from desktop to mobile to cloud, and therefore a more consistent way of handling files both in ODF and OOXML document formats, which improves interoperability. The LibreOffice Technology slide deck provides an extensive description of the concept: https://nextcloud.documentfoundation.org/s/Xw4A7mY6W6yJTqo.

LibreOffice Ecosystem logo is the most important one, so community members should focus their best energies on it. LibreOffice Technology logo would be nice to have, but not as important as the Ecosystem one, as this will be a logo that all community members should use.

As a reference, TDF design and style guides (Corporate Image) are published on the wiki: https://wiki.documentfoundation.org/Marketing/Branding.

Both logos will be used for presentations, event signage, merchandise and gadgets (like stickers). They should be easy to recognize and read even at small sizes.

Both logos logo must be developed with free and open source software, and released in vector-based (SVG) as well as bitmap-based (PNG, JPG) formats. The logo must be available in a square or nearly square version, plus other formats as appropriate. An example of a possible implementation should also be provided with the proposal.

Intellectual property must be released under the Creative Commons Attribution-Share Alike 4.0 License (https://creativecommons.org/licenses/by-sa/4.0/), while a copyright transfer to TDF is not required. The authors must declare in writing that they are the sole owner of all rights related to the artwork they have developed.

It should be clear that this is not a request for a mascot, and any kind of proposal which could be interpreted as a mascot will not be considered. Also, the logo must have a global reach, and as such any reference to a regional styling approach will not be considered.

Logo proposals must be sent to: italo@libreoffice.org by Augus 31, 2021, at 11:59PM UTC. TDF Team will select the winning proposals, which will be announced – and used – during the LibreOffice Virtual Conference, from September 23 to September 25, 2021.

We look forward to meeting the authors of the winning proposals at FOSDEM 2022 in Brussels or at the LibreOffice Conference 2022 (location still to be decided), to celebrate their work.

TDF Annual Report 2020

The Annual Report of The Document Foundation for the year 2020 is now available in PDF format from TDF Nextcloud in three different versions: low resolution (4.7MB), medium resolution (18MB) and high resolution (24.7MB). The annual report is based on the German version presented to the authorities in April.

The 54 page document has been entirely created with free open source software: written contents have obviously been developed with LibreOffice Writer (desktop) and collaboratively modified with LibreOffice Writer (online), charts have been created with LibreOffice Calc and prepared for publishing with LibreOffice Draw, drawings and tables have been developed or modified (from legacy PDF originals) with LibreOffice Draw, images have been prepared for publishing with GIMP, and the layout has been created with Scribus based on the existing templates.

All pictures are licensed under the Creative Commons Attribution-Share Alike 4.0 License, courtesy of TDF Members from all over the world. Stock photos are CC0 by Pixabay.

Lothar Becker, Chairman of TDF Board of Directors, has written in the welcome address:

You will learn that our jubilee year was one of the most successful in our history. With all activities that took place, despite the situation that we could rarely meet in-person, it is really really incredible how the local communities and all supra-national activities carried on. And furthermore we grew in every aspect: our community base has more contributors than ever, and we had an impressive number of releases of LibreOffice, with a lot of code contributions – especially for the new major release of LibreOffice 7.0. And last but not least, the financial report of the foundation shows a year better than ever.

Certainly, we also had some shortfalls last year, starting with the lack of personal meetings and the consequences in the relationships between members – but also with changes and moves in the community and its ecosystem within. And let’s not forget the members of the community who suffered from bad health because of the pandemic situation. But overall, we could feel lucky and proud coming out of this year strengthened as described in this annual report. For all shortfalls, we are working hard in all TDF bodies (the Board, the old and new Membership Committee, the Advisory Board, the team led by Florian Effenberger), with the whole membership as well as national and international parts of the community.

So for all these activities, code and non-code contributions, personal engagements and donations we truly say a big THANK YOU, thank all of you for being with TDF in such a special year for every one of us.

Tender to implement the new TDF Membership Committee’s web-based tooling (#202105-01)

Introduction

The Document Foundation (TDF) is the charitable entity behind the world’s leading free/libre/open source (FLOSS) office suite LibreOffice.

The main activity of the Foundation’s Membership Committee (MC) is to administer membership applications and renewals following the criteria defined in the Foundation’s statutes.

Tender description

We are looking for an individual or company to implement the new TDF Membership Committee’s web-based tooling.

The tasks consists of developing and implementing this tooling. All of the mentioned features and requirements are explained in detail in the provided document “MC tooling specifications”, which is to be considered a part of this tender. The document lists which items are a part of the deliverables and therefore have to be part of the bid.

Note that this tender also contain some optional items, which are marked respectively. All items that are not explicitly marked as optional are to be considered mandatory.

The solution we seek, and as such the scope of this tender, is to implement the new TDF Membership Committee’s web-based tooling that will support the Membership Committee during the daily business.

Decision criteria

All technology standards of relevance, as well as their targeted versions for this tender should be declared or defined in the offer’s description of implementation.

Amongst the decision criteria for the bids are qualification, references, price, and completeness of fulfillment, as well as documentation. We expect bidders to provide documentation on the code, optionally also on the system administrator part.

Requirements

We prefer the use of a secure programming environment. As such, we strongly prefer Python/Django or Ruby on Rails over PHP. The use of server-side Java has to be discussed with TDF’s infrastructure team before bidding. In order to do so, please get in touch with us using the e-mail address below.

We strongly prefer the use of FOSS software and libraries, i.e. for DBMS, crypto and mailing.

The delivered software, code, documentation and all associated parts shall be published under an OSI approved license (see https://opensource.org/licenses) with TDF as owner of the copyright as well as all transferable rights. TDF intends to make the deliverables available to the general public.

Proposed milestones

Milestone #1 – Defining of the architecture; initial prototype with testing and knowledge sharing (with the Membership Committee) about the new solution; usability improvements. Main process elements like voting are tested and work fine. Implementation of the database and the management back-end user interface to interact with it. Import of member information from the old database.

Access to the current production database can be granted to the successful bidder after signing a privacy and non-disclosure agreement. Otherwise, and less preferred, a database with anonymized sample data will be provided.

Milestone #2 – Handling of a new request to become a member of TDF.

Milestone #3 – Have the membership renewal process working.

Milestone #4 – Move the full daily work of the membership committee to the new platform; all voting can be done directly with the new platform. The implementation of reporting and mail system must be completely functional for:

  • Receipt of application
  • Mail for accepted applicants
  • Mail for denied applicants
  • Mail for pending applicants
  • Quarterly report on accepted members in English
  • Quarterly report on accepted members in German

Milestone #5 – Implement and test:

  • Reminders for MC members
  • All time-triggered jobs
  • Quarterly report as CSV file
  • Database integrity check by checking the signature and re-reading this file
  • Deleting of obsolete records cleanup

Required skills

  • Extensive knowledge of Python/Django or Ruby on Rails
  • Extensive knowledge of front-end and back-end development of web-based applications
  • Extensive knowledge of design and implementation of accessible web-based applications
  • Experience in working on open source projects

Other skills

  • English (conversationally fluent in order to coordinate and plan with members of TDF)

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

Bidders will get a preference for including a partner or independent developer who has not been involved in a successful tender before.

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

The task offered is a project-based one-off, with no immediate plans to a mid- or long-term contractual relationship. It is offered on a freelance, project basis. Individuals and companies applying can be located anywhere in the world.

TDF is looking forward to receiving your applications for the aforementioned tasks, your offer in form of a fixed-time, fixed-budget approach, and the duration period for the implementation in calendar weeks of the mentioned milestones after the final awarding of the tender, via e-mail to a committee at tender20210501@documentfoundation.org no later than June 23, 2021.

Applicants who have not received feedback by July 21, 2021 should consider that their application, after careful review, was not accepted.

All bidders are invited to ask their questions on this tender until June 11, 2021. Questions can be sent informally to the above e-mail address, and answers will be made public in a collected and anonymized form.

Projects selected for LibreOffice in the Google Summer of Code 2021

In March, we announced that LibreOffice will be participating in the Google Summer of Code (GSoC), a programme that connects students with free and open source software projects. GSoC helps students to implement new features, and provides them with financial support along the way.

Well, the projects have been selected, so here they are!

  • Bayram Çiçek – 100 Paper Cuts: This aims to improve LibreOffice’s user interface, implementing enhancement requests and solving the most annoying UX (user experience) issues.
  • Anshu Khare – Sidebar: It’s planned to revamp the current styles deck sidebar and to merge paragraph and character styles into one Text Style deck. Furthermore, the student wants to rework the filter workflow. Here’s a mockup (click for larger):

  • Tushar Kumar – Implement an interface for external data source import in Calc: Currently, Calc’s back-end data provider supports CSV, HTML, XML and and Base’s data provider. This feature is not yet ready for production, however, so this project’s goal is to improve it. Here’s a mockup:

  • Balázs Sántha – Implement table styles in OOXML (.docx) support: At the moment, table styles found in .docx documents are converted into direct formatting at at Writer’s core level. This project aims to take a step towards a solution for handling proper table styles.

  • Panos Korovesis – Make the SVM format independent of the VCL metafile + tests for the format: This requires the completion of the tests regarding SVM, and then the separation of the read and write functionality of MetaActions to new distinct classes.
  • Akshit Kushwaha – Tests for the VCL graphics back-end: Add more test cases to the pre-existing tests, running those tests in every back-end, and implement a usable UI for the users to test the graphic’s feasibility themselves. This should make graphics rendering smoother.
  • Shubham Jain – Write missing unit tests: Extend the tests in Libreoffice. There are currently more than 1300 bugs fixes which do not have tests written for them, so this project aims to bring down that number.

Good luck to all the students – we appreciate their work on these important features and improvements! And thanks to our mentors for assisting them: Heiko Tietze, Xisco Fauli, lmari Lauhakangas, Olivier Hallot and Christian Lohmeier (The Document Foundation); Tomaž Vajngerl, Muhammet Kara, Luboš Luňák, Miklos Vajna and Mike Kaganski (Collabora); Thorsten Behrens (allotropia); László Németh and Markus Mohrhard.

From August 16 – 23, students will submit their code, project summaries, and final evaluations of their mentors. Find out more about the timeline here, and check out more details about the projects on this page.