Eight more videos from the LibreOffice Conference 2024

We’re editing and uploading more videos from our recent conference – these ones covering the Google Summer of Code, new Calc functions and optimisations, improvements to language support and more (use the icon in the top-right to choose videos from the playlist):

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

YouTube privacy policy

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

Interview: Jonathan Clark, team member, developer focusing on RTL / CTL / CJK

Hello Jonathan, you have been hired by The Document Foundation in the role of developer focusing on the issues of languages written from right to left, or RTL (Right to Left).

Not only RTL topics – also CTL (Complex Text Layout), and CJK (Chinese-Japanese-Korean). I wanted to point this out, first for the interest of those communities, and second because I feel strongly about the scope The Document Foundation has chosen for this role.

In order to have great language support, I think you need to have two different kinds of people working together: those who can speak to the incredible depth of specific languages and the unique needs of the people who use them; and generalists who can, in the limit, think about all languages, and thus avoid oversights that will prove costly in the long term. I see this role as much closer to the latter than to the former.

Let’s start with a short biography: your origins, your studies, your professional experiences.

My origin is the Canadian wilderness. My parents introduced me to PC games when I was young, and I was instantly and insatiably curious about how they worked. I learned C++, and that eventually led to an undergraduate degree in Computing Science from the University of Alberta.

Most of my professional experience has been working on commercial C++ software quality tools, both as an individual contributor and by providing technical leadership.

For the past few years, I’ve been doing a deep dive on modern game engine technologies as a passion project. Among many other topics, this included real-time text layout and hardware-accelerated text rasterization.

When and how did you approach open source software?

As a user, I can’t remember a time when I didn’t use open source software in one way or another. I’ve never felt comfortable trusting closed-source software for anything important, and that discomfort has only grown over time as business practices change.

As a developer, I’m a bit of a hypocrite – other than a few small projects, I haven’t contributed much. However, speaking both normatively and from experience, I firmly believe that the only way to deliver quality software is with the transparency and accountability of open source.

Why did you decide to respond to The Document Foundation’s job search?

I think it’s important. I want to help people use open source software to work and create in their own language.

There are other reasons, too: I’m a long-time user, interested in linguistics, and my background seemed like a good fit for the role. But the most important thing to me is that I can believe in the mission.

What is your experience as a developer, and why do you think you can contribute significantly to LibreOffice?

As an individual contributor, I’ve been using C++ for a long time and I’m comfortable with large code bases. I’d never looked at the LibreOffice source code before, but it’s similar to projects I’ve worked on in the past.

Finally, what is your feedback after the first few months in the LibreOffice project?

The main feedback I want to offer is praise for the new contributor outreach effort. Most open source projects seem to treat this as an afterthought, but a lot of work has been put into attracting, guiding, and retaining new LibreOffice contributors. It’s wonderful to see.

It’s also been great to see the passion from the community about improving language support.

FOSDEM 2025: LibreOffice Technology DevRoom Call for Papers

FOSDEM 2025 will be only in person, taking place on Saturday, February 1, and Sunday, February 2. LibreOffice Technology DevRoom is scheduled for the morning of Saturday, February 1, from 10AM to 2PM.

IMPORTANT DATES TO REMEMBER

Submission open: 30th October 2024
Submission deadline: 1st December 2024 at 11:59PM CET
Acceptance notifications: 6th December 2024
Final confirmation deadline: 12th December 2024
Final schedule announcement: 15th December 2024
Devroom: 1st February 2025 from 10AM to 2PM

Please note that the submission deadline is managed by the FOSDEM team and not by the devroom managers, which means that after that deadline nothing will be accepted.

We might update this call for papers with further details, as soon as we receive them from FOSDEM organizers. Please check TDF blog and social media channels on a regular basis.

CALL FOR PAPERS

We are inviting proposals for talks about “LibreOffice Technology, a development platform for desktop, mobile and cloud office suites“.

Main topics are LibreOffice development, localization, QA, UX, documentation, extensions, migrations and general advocacy, plus the native document format ODF. Please keep in mind that product pitches are not allowed at FOSDEM.

In order to fit as many presenters as possible in the schedule, the length of talks will be limited to a maximum of 20 minutes, including questions, according to the number of submissions.

TALK SUBMISSIONS

FOSDEM Pretalx system will be open for applications starting from October the 30th, 2024.

To submit a talk, please visit the FOSDEM 2025 Pretalx website: https://pretalx.fosdem.org/fosdem-2025/cfp. Please select “LibreOffice” as the *track* and ensure you include all the requested information when submitting a proposal: the title of the talk, a short abstract (one / two paragraphs), some information about yourself (name, bio and photo, but please do remember that your profile might be already stored in Pretalx).

If you already have a Pretalx account from last year, even if your talk was not accepted, please reuse it. Create an account if, and only if, you don’t have one from a previous year. The system is the same used for LibreOffice Conference, so you should not have issues with Pretalx, but in case you have please contact italo at libreoffice.org for help.

All presentations will be recorded and streamed. Sending your proposal implies giving permission to be recorded.

For accepted talks, speakers will receive an email to confirm that the proposal has been accepted. They may expect additional emails with more instructions, for instance to confirm their travel schedule.

CONTACTS

Italo Vignoli: italo at documentfoundation.org
Michael Meeks: michael.meeks at collabora.com

Community Member Monday: Ritobroto Mukherjee

Ritobroto Mukherjee

Tell us a bit about yourself!

I live in Delhi, India, where I’m working my way towards a bachelor’s degree in IT with a focus on network security at Netaji Subhas University of Technology.

My journey into programming began with QBASIC in school, sparking a love for coding. Since then, I’ve explored everything from game development to operating system internals, embedded systems to mobile apps – anything that catches my interest. My hobbies include learning random science-y things, binge-watching sitcoms, and working late nights only to fall asleep in the middle of the next day 😛

Before the Google Summer of Code (GSoC), my open-source experience was mostly limited to personal projects. Now, I’m much more comfortable filing bug reports, submitting patches, and engaging in code reviews. I also feel more confident in discussing problems and solutions with people I consider far more knowledgeable than me.

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

I recently completed upgrading the .NET Bindings for UNO as part of GSoC 2024.

Currently, I’m on a short hiatus for exams and personal projects, but I’ve been chipping away at the next item on my future work checklist: adding support for in-process bridging, thus enabling LibreOffice extensions to be created with the new .NET Bindings.

Why did you choose to join the project, and how was the experience?

Since switching to Linux a while back, I’ve almost become dependent on the LibreOffice suite to get me through university, having used it for everything from assignments to presentations. The chance to give back to this amazing project, to gain the experience of participating in GSoC, and to tackle a complex .NET and C++ project all at once was too good to pass up.

My experience with the LibreOffice community has been nothing but positive, especially with my mentors, Mr. Hossein Nourikhah and Mr. Thorsten Behrens. Their guidance, paired with the freedom they gave me to make my own decisions on the bindings, was integral to the project’s success.

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

I’m planning on continuing the .NET Bindings project. While the core of the bindings was completed in time for GSoC, there’s still more features, documentation, and examples to work on.

Additionally, I believe LibreOffice needs more documentation, especially for legacy code. Much of my GSoC time was spent understanding the existing bindings before I could start work on the new ones. Using what all I’ve figured out, I want to try and help the Docs team document the bindings better. I might also consider working on introducing more languages bindings in the future.

Big thanks to Ritobroto for all his contributions! Everyone is welcome to join our community, build new skills, and help to make LibreOffice even better for the whole world 😊

Join the LibreOffice Development Workshop at our upcoming conference!

LibreOffice Conference 2024 logo

Hossein Nourikhah, our Developer Community Architect, writes:

Learn LibreOffice development and boost your software skills including bug management, coding, version management using Git, code review using Gerrit and much more! Our workshop titled “Introduction to LibreOffice development” at the LibreOffice Conference 2024 is a great opportunity for all those who love getting involved with a world wide open source community.

Please register soon!

This year, the LibreOffice Conference 2024 will be held in Luxembourg. Alongside the main conference tracks, a development workshop will be held to give the people hands-on experience to LibreOffice development.

The workshop will be held on 11 and 12 October 2024, at the same place as the LibreOffice Conference in Luxembourg. If you like to be with us, please register here:

Learn From Experienced LibreOffice Contributors

Many people from The Document Foundation (TDF), the charity behind LibreOffice will present different topics in the workshop. Also, other contributors and also experienced developers from the ecosystem companies will participate.

We are excited to be able to see you in person in Luxembourg to share practical knowledge about LibreOffice and open source development model with you.

Workshop Topics

These are the topics of the workshop. For more information, please refer to the workshop page at the conference website:

Day One: 11 October 2024

Morning:

1. Bug reporting and triaging (1 hour)
Presenter: Xisco Faulí

2. Git Basics (1 hour)
Presenter: Michael Weghorn

3. Gerrit for code reviews (1 hour)
Presenter: Xisco Faulí

4. Introduction to problem solving techniques (30 minutes)
Presenter: Michael Meeks, Collabora Productivity

Afternoon:

5. Building LibreOffice from source code (3 hours)
Presenter: Christian Lohmaier

6. Introduction to LibreOffice Writer Development (1 hour)
Presenter: Miklos Vajna, Collabora Productivity

Day Two: 12 October 2024

Morning:

7. LibreOffice Documentation (1 hour)
Presenter: Olivier Hallot

8. LibreOffice automation via scripting (BASIC, Python) (3 hours)
Presenter: Rafael Lima / Alain Romedenne / Jean-Pierre Ledure

Requirements

The workshop is based on “bring your own device”. For the scripting, you will need a working LibreOffice installation. You will need to install some development tools and libraries to be able to compile LibreOffice from source code.

But, we will be there in-person at the workshop to help you install the requirements step by step!

What Can You Expect?

After successful participation in the workshop, you can gain better understanding the open source development model, bug reporting and triaging, get started with Git and Gerrit, and also build and run your modified LibreOffice from source code. You will also understand the basic structure of the LibreOffice source code, which will help you to start LibreOffice development.

Click here to register

Community Member Monday: Khushi Gautam

Khushi Gautam

Tell us a bit about yourself!

Hi, I am so glad to be a part of this community. I live in Delhi, India. Currently, I am a software developer serving at Amazon MiniTV.

I have experience in both frontend and backend development for mobile and web applications. I graduated a year ago with a Bachelor of Technology in Computer Science and Engineering from Harcourt Butler Technical University.

I’ve been involved in the open source community since my first year of undergrad, starting with AnitaB, and then moving on to ODK-X. My major contributions have been to LibreOffice.

In my free time, I love writing articles, trying out different cuisines, and meeting new people. I also enjoy traveling and exploring new places with my friends and family.

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

I’m currently working on fixing bugs in my Outreachy project, “Sidebar Deck for Quick Find”, alongside Google Summer of Code students to make further progress. This feature was something I created during my internship at LibreOffice.

Why did you choose to join the project, and how was the experience?

LibreOffice includes applications like Writer, Calc, Impress, Draw, and Base, and is the default suite for Linux. I started my journey with LibreOffice as an Outreachy applicant, which was my first time contributing to LibreOffice and interacting with other developers on the IRC channel. After researching various organizations and projects, I chose to contribute to the “Sidebar Deck for Quick Find” project because it aligned with my skills as a C++ developer.

LibreOffice screenshot: Sidebar Deck for Quick Find

Weekly mentoring chats with Ilmari Lauhakangas were incredibly helpful during the contribution phase. He guided me in setting up my project locally and introduced me to starter tasks, which made me more comfortable with the project and the organization. I also learned to operate Gerrit and successfully made my first patch.

Later, I was selected as an Outreachy intern to work on the “Sidebar Deck for Quick Find” project. My mentors, Jim Raykowski and Heiko Tietze, were instrumental in making the project successful. I was thrilled when my patch for the feature was merged after three months of hard work.

My experience with LibreOffice was enriching, as I got to work closely with the entire codebase, something I always wanted to do. The community is very supportive, and I’m looking forward to meeting them in person at the upcoming conference.

Anything else you plan to do in the future?

These days, I’m aiming to join a multinational corporation as a backend developer and hope to achieve this goal soon. I also aspire to join LibreOffice as a developer. Even though I’m already contributing, I love that open source allows me to continue working freely. Additionally, I plan to create a wiki for the feature I’ve developed and take ownership of presenting it to the world upon its launch.

What does LibreOffice really need?

I would say: more developers and contributors like me!

Big thanks to Khushi for all her contributions! Everyone is welcome to join our community, build new skills, and help to make LibreOffice even better for the whole world 😊