Sophie Gautier talks about the project

You are one of the people who have been around from the beginning of The Document Foundation, and one of the oldest members of the community (including the years of OpenOffice.Org). How were you involved in the project?

I was using StarOffice 5.2 and was contributing support on the French speaking users list. When Sun Microsystems was about to open source the code and create the OpenOffice.org project, they invited me to join and support the community. From there, I’ve been involved in various tasks like localization, quality assurance or documentation.

We are getting close to the 10th anniversary of the LibreOffice project, and the 20th anniversary of the FLOSS office suite. Which are the milestones of this long history?

I may not remember all of them, but I guess the creation of the Native Language projects with the French speaking one as a Proof of Concept in 2001. Then the many community supported projects such as marketing, documentation, etc.

And then of course, the birth of the LibreOffice project. Since then I’ve the impression that each year is a milestone 😉

There have been so many exciting things to do in each corner of the project. The community is pushing a lot of good ideas and energy. Considering the work done on QA, UX/Design and marketing for the product or the community, the new help system and the size of our infra, we have achieved more than we could even imagine ten years ago!

You have been involved in the localization of the software since the very first version, and now you are coordinating the activity of native language projects. Can you talk about the localization activity?

Localization is a complicated task, and sometime tedious. LibreOffice is a big software with thousands of different strings. Localization happens at the end of the software making process, so the workload depends on development, UX/Design and marketing projects.

Recently, there have been changes on the strings format for almost the entire interface of each module, on the help system and more and more marketing activities. Each localization member should be very proud of his/her work.

We want to cover more languages because localization is a way to preserve those languages, preserve the local culture and give all users the opportunity to express themselves in their own language. This is where my activities lie: understand the needs of localizers, voice their concerns, update the workflow and try to make them happy to translate the different projects.

You have been a member of the team for almost six years, with a number of different responsibilities. From your point of view, how well did the project during this time?

Happy to say: fairly well 🙂 The task was not easy but I believe we are doing right. Some people would like to see more things happening, or the project going faster or further. But we are a diverse community with different cultures, different business or occupations and different time zones!

We need to keep people together on the same path, to preserve the soul of the project. It’s not easy to keep an eye on the horizon on a daily basis, but our directors are doing that since the beginning and they are doing it very well if you look at the foundation’s results.

I can see my colleagues of the team working hard on each critical part of the production process, and at the same time taking care of the community, trying to answer end user questions and help independently from what they have on the table. I’m proud and very happy to be part of this team, and happy to see how mature the foundation has became. Every day I’m learning something new, either from them or from the community. I’m thankful for that 🙂

With the growth of the project and the community, you are now moving to the position of Foundation Coordinator. Can you describe this role?

I’m taking care of several foundation activities, like helping to organize LibOCon and Advisory Board meetings, and handling several administrative tasks. I’m also directly involved in L10n/NL, marketing and certification projects.

I follow what is happening in other parts of the project, and try to bring my help and my knowledge where needed. For example, when the work began on the UX, I helped the team with my knowledge of the product and its philosophy.

The change will happen mainly in the administrative parts, where an assistant will be hired by the foundation. That should leave me more time to push some projects we want to put in place, like the travel support program, Open Badges, moving to another translation tool, etc.

Looking at the next decade, which are the top challenges for LibreOffice?

One of the most important challenges for open source projects is to make the community of volunteers and ecosystem participants thrive. Our developers are securing this by constantly enhancing tools and processes, but at the same time users and contributors are evolving, and we need to reinvent ourselves almost every day. This also means to re-evaluate processes and tools, looking at them in perspective.

Last, but not least, the product has to further evolve according to changes in the market, and we have to invest to make the online version more popular amongst users and increase the number of adoptions and contributions to the project.

OASIS announces the ODF Advocacy Open Project

The ODF Advocacy Open Project we have pre-announced at FOSDEM is now a reality. Yesterday, OASIS has released the following press release, which is just the first step of a new sustained activity focused on supporting the adoption of ODF – the only true standard document format available on the market – by governments, public administrations and enterprises worldwide, to increase interoperability (and thus knowledge sharing), reduce hidden costs associated to document management, and get rid of vendor lock-in.

OASIS Introduces Open Projects Program to Bridge Open Source and Standards Development

AirBus, CIB, Fujitsu, IBM, Red Hat, Siemens, Software AG, The Document Foundation, and others sponsor Open Projects

Boston, May 8, 2019 – OASIS, a global nonprofit consortium, today announced the launch of Open Projects, the first-of-its-kind program that creates a more transparent and collaborative future for open source and standards development. Open Projects gives communities the power to develop what they choose–APIs, code, specifications, reference implementations, guidelines– in one place, under open source licenses, with a path to recognition in global policy and procurement.

The lines between open source and open standards have been blurring for some time, and communities in both arenas have been calling for more flexibility and options for collaboration. Open Projects is a new approach that addresses the need for change in everything from handling IP to governance and decision-making, from funding to establishing trust and assuring quality.

“With Open Projects, we’re building a movement to transform the open source and standards world,” said Gershon Janssen, Chairman, OASIS Board of Directors. “We want to dissolve the barriers that separate communities. We want to empower groups with more control and streamlined governance. We want to support projects by giving them all the process they need–and not a bit more–so they can accomplish great things fast.”

Open Projects builds on the OASIS experience and reputation for producing quality work that’s been trusted and supported by governments and industries worldwide for more than 25 years.

“For many, open source has become a means of establishing de facto software standards. However, de facto standards are not recognized by many governments and institutions,” said Chris Ferris, IBM Fellow and CTO Open Tech for IBM. “OASIS Open Projects provides an important new opportunity to leverage the rapid innovation of open source in the process of developing open standards. The potential to achieve ISO, IEC, or ITU standards approval is a huge value for many important open source initiatives.” Ferris, who also holds a leadership position on the Hyperledger Fabric project, played an instrumental role in defining the OASIS Open Projects program and now serves on its Advisory Council.

The Open Projects program is being advanced by some of the most accomplished, regarded minds in open source today.

As part of the program announcement, OASIS is launching the first two Open Projects – Open Services for Lifecycle Collaboration (OSLC) and OpenDocument Format (ODF) Advocacy.

The OSLC Open Project advances a suite of standard REST APIs to connect data and achieve the digital thread across domains, applications, and organizations. It is sponsored by AirBus, Austrian Institute of Technology, Bank of America, Boeing, Dassault, Fujitsu, IBM, Koneksys, KTH Royal Institute of Technology, Red Hat, Siemens, Software AG, and Tasktop.

“OSLC helps create standard REST APIs that solve industry integration challenges,” said Andrew Berezovskyi of the KTH Royal Institute of Technology. “Open Projects enables the OSLC community to produce deliverables that meet requirements from various stakeholders without being hindered by the weight of foundation bureaucracy or the baggage that comes with financial, legal, technical, and marketing administration.”

The ODF Advocacy Open Project promotes the world’s leading document standard. After being approved as an OASIS Standard, ODF was recognized by ISO/IEC and endorsed by governments around the world as a way to ensure permanent access to data and eliminate the risk of vendor lock-in. The ODF Advocacy Open Project is sponsored by CIB and The Document Foundation.

“ODF guarantees perennial access to data that can be transferred in a transparent way between different apps, computers and operating systems, getting rid of hidden interoperability costs, vendor lock-in issues and license fees,” said Italo Vignoli, Co-Founder, The Document Foundation.

Additional Open Projects for blockchain and other areas will be announced in the coming months. Further details about OASIS Open Projects are available here or email info@oasis-open-projects.org.

First Bug Hunting Session for LibreOffice 6.3

LibreOffice 6.3 is being developed by our worldwide community, and is due to be released in early August 2019 (see release notes describing the new features here).

In order to find, report and triage bugs, the LibreOffice QA team is organizing the first Bug Hunting Session for LibreOffice 6.3 on Monday May 13, 2019. Tests will be performed on the first Alpha version, which will be available on the pre-releases server a few days before the event. Builds will be available for Linux (DEB and RPM), macOS and Windows, and can be installed and run in parallel along with the production version.

Mentors will be available from 07:00 UTC to 19:00 UTC for questions or help in the IRC channel #libreoffice-qa and the Telegram QA Channel. Of course, hunting bugs will be possible also on other days, as the builds of this particular Alpha release (LibreOffice 6.3.0 Alpha 1) will be available until the end of May. Check the Release Plan.

During the day there will be a dedicated session to test the ongoing work in the KDE5 integration from 14:00 and 16:00 UTC.

All details of the first bug hunting session are available on the wiki.

Release of LibreOffice 6.1.6

Berlin, May 7, 2019 – The Document Foundation announces LibreOffice 6.1.6, the 6th minor release of the LibreOffice 6.1 family, targeted to users in production environments. This is a more mature version of the software which includes some months of back-ported fixes.

LibreOffice 6.1.6’s change log pages, with a list of bug and regression fixes, are available on TDF’s wiki: https://wiki.documentfoundation.org/Releases/6.1.6/RC1 (changed in RC1) https://wiki.documentfoundation.org/Releases/6.1.6/RC2 (changed in RC2) and https://wiki.documentfoundation.org/Releases/6.1.6/RC3 (changed in RC3).

LibreOffice users are invited to join the community at https://ask.libreoffice.org, where they can get and provide user-to-user support. While TDF can not provide commercial level support, there are guides, manuals, tutorials and HowTos on the website and the wiki. Your donations help us make these available.

Enterprise Deployments

Organizations looking for an enterprise class application backed by support and service level agreements (SLA) should source a LibreOffice LTS (Long Term Supported) version from those TDF Advisory Board members who provide this product (https://www.documentfoundation.org/governance/advisory-board/).

Also, value-added services for enterprise class deployments – related to software support, migrations and training – should be sourced from certified professionals (https://www.libreoffice.org/get-help/professional-support/).

Sourcing software and/or services from the ecosystem of certified professionals represents the best support option for enterprises deploying LibreOffice on a large number of desktops. In fact, these activities are contributed back to the project under the form of improvements to the software and the community, and trigger a virtuous circle which is beneficial to users and all other stakeholders.

Availability of LibreOffice 6.1.6

LibreOffice 6.1.6 is immediately available from the following link: https://www.libreoffice.org/download/. Minimum requirements for proprietary operating systems are Microsoft Windows 7 SP1 and Apple macOS 10.9. Builds of the latest LibreOffice Online source code are also available as Docker images: https://hub.docker.com/r/libreoffice/online/.

LibreOffice Online is fundamentally a server-based platform, and should be installed and configured by adding cloud storage and an SSL certificate. It might be considered an enabling technology for the cloud services offered by ISPs or the private cloud of enterprises and large organizations.

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

LibreOffice 6.1.6 is built with document conversion libraries from the Document Liberation Project: https://www.documentliberation.org.

TDF is Google Seasons of Doc Mentoring Organization

The Document Foundation has been accepted as organization for the Google Seasons of Docs, a project whose goals are to give technical writers an opportunity to gain experience in contributing to open source projects, and to give open source projects an opportunity to engage the technical writing community.

For technical writers who are new to open source, the program provides an opportunity to gain experience in contributing to open source projects. For technical writers who’re already working in open source, the program provides a potentially new way of working together.

During the program, technical writers will spend a few months working closely with the LibreOffice community, bringing their technical writing expertise to the project’s documentation, and at the same time learn about the open source project and new technologies. At the same time, LibreOffice documentation team members will work with the technical writers to improve the project’s documentation and processes.

LibreOffice is an advanced office suite covering may areas of knowledge, from maths and sciences, engineering, financials, editing, drawing, printing and more. LibreOffice is also that kind of application that is used cross-industry, a very rich opportunity for technical writing.

Olivier Hallot, LibreOffice documentation coordinator, will lead the GSoD project, supported by Sophie Gautier and by members of the LibreOffice documentation team such as Drew Jensen, who has immediately created a banner to visually support this community effort.

All information about the Google Summer of Docs project are on the GSoD website. An outline of the project’s different steps is available on the GSoD timeline. The next deadline in the process for The Document Foundation is May 28th, as we we have to find interested technical writers to discuss our ideas, which are summarized on the following TDF wiki page. The list includes some of our project’s permanent challenges, but should not be limited to these items.

LibreOffice contributors who are interested in becoming a mentor for the GSoD project should get in touch with Olivier Hallot by sending him a message or by subscribing to the documentation mailing list.

Reminder: LibOCon 2020 Call for Locations

The Call for Location for LibreOffice Conference 2020 is open until June 30, 2019. It will be the 10th of a series of successful events: Paris, October 2011; Berlin, October 2012; Milan, September 2013; Bern, September 2014; Aarhus, September 2015; Brno, September 2016; Rome, October 2017; Tirana, September 2018, and Almeria, September 2019. During or around the event we will celebrate the 10th anniversary of the project, which was announced on September 28, 2010.

The Call for Locations opens well in advance as TDF Board of Directors wants to to give the event organizers the opportunity to attend this year’s conference – in Almeria, Spain, September 11 to 13, 2019 – to familiarize with the community and the structure of the event. For historical and practical reasons, the LibreOffice Conference takes place between September and November, with a preference for September.

More details about LibOCon 2020 Call for Locations are available on the original blog post.