Home » Development » Page 11

Category: Development

Bug Hunting Session for LibreOffice 7.1 Alpha

LibreOffice 7.1 is being developed by our worldwide community, and is due to be released in early February 2021 – see the 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 7.1 on Monday October 26, 2020. Tests will be performed on the first Alpha version. 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 7.1.0 Alpha1) will be available until mid November. Check the Release Plan.

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

Tender to finish transition of LibreOffice to ODF 1.3 (ODF 1.3 delta) (#202010-01)

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

We are looking for an individual or company to finish transition of LibreOffice to ODF 1.3 (ODF 1.3 delta).

This tender builds on the previous ODF 1.3 tender and aims to implement additional features.

The work has to be developed on LibreOffice master, so that it will be released in the next major version.

The following required features (section A) need to be implemented:

  • chart:data-label-series. Missing feature. It is needed for import from Excel.
    • Relevant bugs in TDF’s Bugzilla: #94235, #133176
    • OASIS reference: OFFICE-2117
  • chart:regression-moving-type. Implementation of types “center” and “average-abscissa” is missing. It is needed for interoperability with Gnumeric.
    • For this feature, there is existing code that can be extended.
    • Relevant bug in TDF’s Bugzilla: #133423
    • OASIS reference: OFFICE-3959
  • <text:index-entry-link-start> and <text:index-entry-link-end> in user-index. The link marks exist, but the function itself is not implemented.
    • For this feature, there is existing code that can be extended.
    • Relevant bug in TDF’s Bugzilla: #121842
    • OASIS reference: OFFICE-3941

The following are desirable features (section B):

  • draw:fill for background of pages. Attribute draw:background-size specifies whether a background fill covers the entire page or only the content area of the page. It belongs to element <style:drawing-page-properties>. ODF 1.3 has extended its use to all kind of pages. Some related bug reports have been set to “fixed”, but the problem is not completely solved, details in the bug report.
    • The respective attribute seems to get written by LibreOffice already. All Writer documents are now the entire page.
    • Relevant bug in TDF’s Bugzilla: #134734
    • OASIS reference: OFFICE-3937
  • draw:z-index more precise with increase from back to front. Problem needs to be solved too for cases when converting from docx to odt.
    • Relevant bug in TDF’s Bugzilla: #133487
    • OASIS reference: OFFICE-2122

The following features are nice to have (section C):

  • Wrong icon of master document template in Windows Explorer
    • Relevant bug in TDF’s Bugzilla: #133285
    • OASIS reference: OFFICE-2580
  • pivot table based on named range with local scope
    • The previous implementation didn’t work out. This is a rather complex task.
    • Relevant bug in TDF’s Bugzilla: #37268
    • OASIS reference: OFFICE-3665

The following features are purely optional (section D):

  • Adapt function wizard to the fact, that the second parameter of DCOUNT and DCOUNTA may be empty (i.e. optional)
    • This can be qualified as an “EasyHack”.
    • OASIS reference: OFFICE-3906
  • chart:coordinate-region. There is no help about this topic. There exists no option to not use this kind of position and size reference.
    • That feature was handled differently until OpenOffice.org 3.0, where the coordinates included the description, now they are without, i.e. the reference changed.
    • OASIS reference: OFFICE-3928
  • fo:min-height as attribute of draw:text-box. LibreOffice does not use that attribute and ignores it on file open. Missing feature.
    • That element seems to be written by Word, but likely not yet by LibreOffice.
    • OASIS reference: OFFICE-3735

The following feature is purely optional, and not trivial from a UX point of view (section E):

  • svg:stroke-linecap at object style vs draw:style in element. Implementation of draw:style is incomplete. Especially there is no UI to define a line style with round dashes.
    • Relevant bugs in TDF’s Bugzilla: #133499 (Implementation has error), #127509, #127348, #127266, #123349, #53276, #127207
    • OASIS reference: OFFICE-3742

Required skills

  • Extensive knowledge of C++
  • Experience working on the LibreOffice source code
  • Knowledge of the OpenDocument Format standard, particularly in version 1.3.

Other skills

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

We use free, libre and open source (FLOSS) software for development wherever possible, and the resulting work must be licensed under the Mozilla Public License v2.0.

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 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.

When budgeting, we anticipated that this project (sections A-E) to take in the region of 32 days of work.

TDF is looking forward to receiving your applications for one or more of the aforementioned tasks, your financial expectations and the earliest date of your availability, via e-mail to a committee at tender20201001@documentfoundation.org no later than November 10, 2020.

Applicants who have not received feedback by December 8, 2020 should consider that their application, after careful review, was not accepted.

LibreOffice and Google Summer of Code 2020: The results

Google Summer of Code logo

This year, LibreOffice was once again a mentoring organization in the Google Summer of Code (GSoC) a global programme focused on bringing more student developers into free and open source software development. We ran six projects – and all were finished successfully. Students and mentors enjoyed the time, and here we present some of the achievements, which should make their way into LibreOffice 7.1 in early February 2021!

You can experiment with the new functionality by using daily builds and report any problems in our bug tracker.

Styles Inspector for Writer by Shivam Kumar Singh

Mentors: Tomaž Vajngerl, Mikhail Kaganskiy (Collabora)

Dealing with styles and formatting in complex documents can become tedious, especially when you are working on something you did not create yourself. The Styles Inspector implemented by Shivam conveniently displays all the properties of the elements making up a document. It will surely become an essential tool for Writer experts.

Learn more about the Styles Inspector in the final report.

Styles Inspector

Additions – Tight integration of extensions by Yusuf Keten

Mentor: Muhammet Kara (Collabora)

Thanks to the work of Yusuf, users are now able to fetch extensions, templates and other resources as well as discover guide books without ever leaving LibreOffice.

Learn more about Additions in the final report.

Additions

Extending the UI testing framework by Ahmed ElShreif

Mentor: Markus Mohrhard

A domain-specific language (DSL) for LibreOffice’s Python-based UI testing framework was originally implemented by Saurav Chirania in 2018. Ahmed ElShreif continued the work in 2019 and now tackled further improvements in the DSL and in the testing framework itself. This means that the automated quality assurance system is better at preventing bugs from slipping into LibreOffice.

Learn more about the UI testing project in the final report.

Impress shape animations with a real physics engine by Sarper Akdemir

Mentor: Thorsten Behrens (CIB)

Sarper added the ability to enrich presentations with animations powered by the physics simulator engine Box2D.

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.

Learn more about the physics engine project in the final report.

Moving the gallery code to a friendly format by Aditya Sahu

Mentors: Tomaž Vajngerl, Michael Meeks (Collabora)

It was not simple to work on galleries due to them being stored in a custom binary format. Now Aditya got us out of this unfortunate situation and designers will have a much easier time.

Learn more about the gallery project in the final report.

Blurry shadows by Ahmad Ganzouri

Mentors: Tomaž Vajngerl, Miklos Vajna (Collabora)

Shapes and objects in LibreOffice used to only support hard shadows. Now Ahmad implemented proper blurriness for the shadows, supporting both ODF and OOXML formats.

Blurry shadows

Learn more about blurry shadows in the final report.

Wrapping up

Many thanks to all students who spent their summer time improving LibreOffice. You are awesome! And special thanks also to the mentors who always put so much love and energy into these tasks. That‘s what makes LibreOffice rock.

Now we are looking forward to next year’s GsoC. If you are interested, why not prepare early? Learn more at out wiki page where some ideas are listed. Participating in GSoC is a great way to build your skills, and show future employers what you’re capable of!

Community Member Monday: Pranam Lashkari (Collabora/GSoC)

Today we’re talking to Pranam Lashkari from our Indian community, who is working in the LibreOffice ecosystem at Collabora, improving the web-based version of the suite…

First off, tell us a bit about yourself!

Pranam! (It means namaste, and yes, that’s my name too 😂). I live in Rajkot, a city in the middle of the state of Gujarat in India. I am a computer engineer who started working on open source projects as a student, to expand my knowledge, which later got me into Google Summer of Code – twice as a student, and this year I became a mentor and a maintainer of one of the Boost C++ Libraries called GIL (Generic Image Library).

The eagerness for always working in open source led me to work with Collabora Productivity, where I’m privileged to work full-time to take LibreOffice development further. So far, all the code I have written in my life is open source.

When I am not programming, I like to spend my time playing cricket (or any sport), doing some observational astronomy, or reading things related to science.

You can find me on LinkedIn and GitHub.

What are you working on in the LibreOffice project right now?

Most of my work is focused on LibreOffice Online, which also happens to be the project behind the mobile version of Collabora Office. I started by removing the Poco framework, and then adding major features like smooth scrolling in mobile.

Currently, I am working on desktop browser version of LibreOffice Online, where I try to align features with the core version. On the other hand, in the mobile version, I solve different bugs in mobile wizards and enable new features which are not yet available in mobile. While working on the mobile wizard, I also try to optimize the performance wherever possible by avoiding and reducing unnecessary communication with the server – and making things look more snappy on mobile.

Why did you decide to become a member of The Document Foundation?

I love it when my code is used by people. Having a large number of users of LibreOffice attracted me to be a developer in TDF projects, and I am very thankful to Jan Holesovsky and Michael Meeks for giving me this wonderful opportunity and helping me get started and grow.

At first, I wasn’t aware of the existence of such programmes where one can become a member, until I received an email inviting me to apply to become a member of TDF because of my continuous involvement in TDF projects the last six months. I decided to apply for the membership because it would help me align the development with the goals set by the organisation, and get a clear picture of further required development.

The best way to move forward is by collaborating and becoming a part of the project. By becoming a member, I also wish to give my feedback on decisions and strategies.

Anything else you plan to do in the future? What does LibreOffice really need?

In my work for Collabora, we focus on what our customers and partners most want to be done next – always something interesting.

Finally, one thing I would like to add: working on these projects which are involved in changing the user experience forever is one of the best experiences I have had as a developer. I would like to thank Collabora and TDF for this.

TDF says: we’d like to thank you, Pranam, for all your work! A strong and healthy ecosystem is essential for the future of LibreOffice, so we’re glad you’re enjoying working for Collabora and improving LibreOffice Online. Cheers!

Build your skills – join our online hackfest during the LibreOffice conference!

Who makes LibreOffice? How can you – as a user – get involved in the community? And what can you contribute to the project? Well, we’ll answer all of these questions, and more, in an upcoming online “hackfest” during the LibreOffice conference. This is a virtual event where the world’s foremost LibreOffice experts will be at hand, to answer your questions about contributing to the project. You can see how they work and “how the sausage is made”, as they say!

There are many ways to help out:

  • Designing the user interface
  • Improving the features and functionality with C++ programming
  • Updating the documentation
  • Translating the app and website
  • Starting cool marketing campaigns
  • Confirming bug reports from other users

And much more. By joining a well-known and well-established FOSS project like LibreOffice, you can build up your skillset for future career options. And also meet new people and have fun!

So, do you have a question about contributing? If so, please send your questions to ilmari.lauhakangas@libreoffice.org by 27 September 2020.

A panel of experts will convene to present on your questions and topics. Everyone is welcome to join and ask further questions. In the case that your spontaneous questions render the experts speechless, answers will be provided after the event. The duration of the event is one hour.

We look forward to hearing from you!

Join our team! Job Search for a Development Mentor (m/f/d) – #202007-01

The Document Foundation (TDF) is the non-profit entity behind the world’s leading open source office suite, LibreOffice. It’s comprised of a team of highly skilled and motivated people, working on infrastructure, design, documentation, QA, marketing and other tasks. We’re passionate about free software and bringing people into our community.

To grow our volunteer community, in particular for code contributions, we’re searching for

a Development Mentor (m/f/d)

to start work as soon as possible. If you’re interested in the role, which is offered on a part- or full-time basis, you ideally have:

  • previous experience in remote work
  • been a long-time contributor to one or more FLOSS communities
  • excellent communication skills, with enthusiasm for mentoring – a fluent command of the English language (written and spoken) is expected
  • coding experience in several FLOSS code bases and programming languages, including LibreOffice
  • demonstrable C++ coding experience of at least five years, plus active knowledge of at least one more language used in LibreOffice (e.g. Python or Java)
  • willingness to regularly travel to Hackfests & conferences in Europe and globally
  • self-driven and a good team player; interested in working together with our team

The remote job role involves working from home at your location and includes among other items:

Work with our existing team in the LibreOffice community on topics including:

  • building relationships between the community and new contributors
  • identifying and on-boarding new contributors
  • affirming and encouraging their contribution
  • encouraging them to join IRC and other communication channels to meet the community
  • building relationships with domain experts for deeper learning
  • attracting new contributors by promoting the project
  • interaction with UX volunteers

Shape and create development mentoring including:

  • helping to onboard new contributors by
    • positively reviewing their code contributions
    • improving their C++ programming skills & design, and coding style
    • introducing them to our tooling and culture
  • designing, and define easy tasks for new contributors
  • maintaining our technical documentation, e.g.
    • developer guide
    • wiki articles
    • code comments
  • helping to review the results of development tenders produced by TDF
  • goals-oriented and with a laser-sharp focus to grow excellent LibreOffice core contributors, our perfect candidate will come up with creative ways to find and attract volunteers

Previous experience with such tasks is highly welcome, so is using free software. Speaking and writing English fluently 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).

TDF welcomes applications from all suitably qualified persons regardless of their race, gender, 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 tender20200701@documentfoundation.org no later than September 15, 2020.

If you haven’t received feedback by October 30, 2020, your application could not be considered.

Press Releases

LibreOffice 25.8.5 has arrived

Berlin, 19 February 2026 – LibreOffice 25.8.5, the fifth update to the FOSS office suite [1] developed by volunteers for…

Open Document Format

Why ODF and not OOXML

Many interpreted the last article in this series as an attack on Microsoft for using the OOXML format against users'…