Community Member Monday: Dione Maddern, LibreOffice docs team

Dione Maddern

Today we’re talking to Dione Maddern, who helps out in LibreOffice’s documentation team…

Tell us a bit about yourself!

I’m 44. Originally from Brisbane, Australia but I currently live in Baltimore, on the East Coast of the USA. I’ve worked in a variety of administration, document production roles in the engineering and insurance industries.

Most of my technical writing experience has been writing procedures, instructions, and other documentation for Health Safety Environment and Quality (HSEQ) systems. This is my first software project.

In my spare time, I like to bake, draw, and play video games and tabletop RPGs.

What are you doing in the LibreOffice community at the moment?

I’m working on the Offline Help (F1) function of LibreOffice, fixing broken links and updating instructions and terminology.

How did you join the community, and what was it like?

I saw the banner on the user guide page asking for volunteers to work on Documentation Team. I’d been looking for a volunteer opportunity where I could use my skills in document production for a while and this seemed perfect. So I followed the link and posted my bio on the Documentation forum.

Banner to join the Docs team

I felt a bit daunted at first because a lot people had more experience than me, or were from a software development background. Everyone has been very welcoming and I feel like I’ve been able to make a contribution to the project. I’ve learned a lot too, including a crash course in XML and Gerrit.

What advice would you give to others who want to join the documentation team?

Dive in! It can seem a bit daunting at first, but it’s easier to get started than you think.

Thanks so much to Dione for all the help! Indeed, everyone is welcome to dive in, help out, and pick up valuable experience along the way. Who knows – perhaps it could lead to a career in technical writing…

LibreOffice QA help from CSUMB students – Steven Casey

Steven Casey

The Document Foundation – the non-profit entity behind LibreOffice – recently teamed up with the California State University, Monterey Bay (CSUMB) to encourage students to learn about LibreOffice quality assurance (QA) and help out. A few days ago we chatted with Keldin Maldonado, and today we’re talking to Steven Casey…

What did you work on in your 25 hours?

During my 25 hours, I was primarily tasked with working on bug reports for LibreOffice. At the beginning of my service, I was simply testing unconfirmed reports and retesting confirmed reports to ensure the bugs were still present in the up-to-date version of the software. I would leave comments on those reports about my findings and follow up later if needed. Once I got a better understanding of Bugzilla, the software, and my duties (and I sure did make my fair share of mistakes), I moved on to binary bisecting. Binary bisecting was more advanced than what I was doing before, but it was also quite a bit of fun!

It was common for me to spend hours digging deep into a report to figure out which commit was causing the regression and more importantly, why. As a student studying computer science with an intention of becoming a software engineer, it was important to me to try and figure out why these bugs were happening. Often times, I came up with a theory and happily appended it to my comment on the report, but sometimes I would run into a roadblock and not be able to figure it out.

What was the experience like?

Honestly, the experience was a lot better than I initially expected. I think a large part of that was due to my mentor during my service, Ilmari Lauhakangas. Ilmari was both understanding and extremely helpful, not to mention just a great individual. I was often pretty loaded with work during my service and I really appreciated the no commitment, work on your own time whenever approach. There were some days I would work 5 hours mid-day, and other days where I would work for an hour between 1 and 2 in the morning!

LibreOffice also has a fantastic wiki with a lot of info for beginner bug triagers on getting started which helped a lot, as it was a little overwhelming in the beginning. Thanks to the wiki along with the tutorial videos Ilmari provided, I was able to mostly get a grasp on things pretty quickly. However, the wiki, while holding great information, feels a little scattered. There were a couple of times where I would search for something on the wiki, and end up not finding it to have Ilmari send me a link to a slightly different page I just happened to miss.

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.

For example, there is a GetInvolved page and a BugTriage page, which have very similar info, but some small differences which can be important. While it wasn’t an issue for me, time zones can also be a slight issue for someone who is interested in volunteering. Being based in California in the United States, available meeting times would either be around 10pm or 9am or so. Luckily, I am often up late at night, so 10pm was great for me!

What are you planning to do next?

I still plan to contribute to bugs here and there very casually. I genuinely mean it when I say that this experience was “life changing” no matter how silly that may sound. I graduate in August of 2024 so I plan on focusing on that the most. I do need to be career ready, and secure a position for graduation. With that being said, Ilmari has asked me to email him if I’m interested in LibreOffice development after the holidays. I don’t know what that will entail quite yet, but I plan on taking him up on that offer. Maybe I will be the one accidentally introducing the regressions soon!

Many thanks thanks to Steven and Keldin for their help! All LibreOffice users are welcome to join our QA community and keep the software strong and robust.

LibreOffice QA help from CSUMB students – Keldin Maldonado

Keldin Maldonado

Recently, The Document Foundation – the non-profit entity behind LibreOffice – teamed up with the California State University, Monterey Bay (CSUMB) to encourage students to learn about LibreOffice quality assurance (QA) and help out. Let’s hear from one of the students, Keldin Maldonado:

What did you work on in your 25 hours?

I worked in the QA team for LibreOffice. I was tasked with looking over bug reports and providing feedback on these reports by either confirming the bug, asking for more information, or providing my feedback if I wasn’t able to replicate the bug.

Later in my volunteer time, I learned about finding the specific commits that caused the bugs through bibisecting that made life for developers a lot easier. I must say, it was honestly really cool seeing the open source model in action. I was able to witness the community effort to resolve these issues in LibreOffice and see how this product was consistently improving.

What was the experience like?

This was the first time doing any sort of work like this, so I had a hard time getting used to some of the tooling, specifically Bugzilla with its infinite options. Luckily, I had Ilmari Lauhakangas to mentor me through this. He provided search queries that definitely made life easier. Apart from this, I also had issues with my working environment because of backward compatibility. I was able to use Distrobox, however, on a Linux box I built specifically for bug hunting that I then SSHed into from my main machine to be able to run older versions of LibreOffice, and my compatibility issues disappeared.

Bugzilla logo

In terms of the good things, I genuinely think that the last couple of mentoring meetings that I had with Ilmari taught me things that will stick with me for life, and for that, I have to give him a huge thanks for being patient and a good mentor. Specifically, I think learning about bibisecting was a great skill to be taught. I will definitely continue to use this going into my professional career and participating further in the open source community.

I also think that having a chance to work in this community maintaining LibreOffice, a product that many people rely on a day to day basis, was great. It might sound a bit cliche, but it genuinely felt really good knowing about the impact I was making, albeit small on the grand scheme of things. I know that my efforts made people’s lives a bit easier in the long run.

What are you planning to do next?

In terms of my professional plans, I am still enrolled in my undergraduate computer science program, which I will finish in the summer of 2024, and then I hope to go into software engineering. Currently, that is what’s taking up the majority of my time. In regards to The Document Foundation and LibreOffice, I will continue to provide help. Last I spoke with Ilmari, he asked me if I wanted to continue with the development side of things, which I think is a great opportunity for me to further develop my skill, and it will give me a chance to continue helping with The Document Foundation’s efforts.

Big thanks to Keldin for his contributions! But he wasn’t alone – Steven Casey also joined the QA community, and we’ll talk to him in our next interview on this blog…

Community Member Monday: Dominique Prieur

Map of LibreOffice community members

Today we’re talking to Dominique Prieur, who recently became a member of The Document Foundation, the non-profit entity behind LibreOffice…

Hi! Tell us a bit about yourself…

I’m French (and my English is too poor and too bad). I live in Orléans, 120 km south of Paris. I was in the army for 18 months and then a civil servant for 44 years. I’m now retired. I read a lot, listen to music, play with Python and look at the sky and the stars 🙂 Oh yes, I take a lot of photographs.

What are you doing with LibreOffice right now?

I used to work for the Direction générale des finances publiques (French Treasury). We used LibreOffice exclusively. I managed the finances of large hospitals and had lots of very large CSV files to reprocess. Today, I only do basic office automation. Occasionally, I give free courses on LibreOffice, particularly on styles and regular expressions. I’m working with the Orléans prison to develop office automation workshops with prisoners.

Why did you choose to join the LibreOffice project?

I wanted to join the project to find out how it works “from the inside”. I don’t have much experience of it yet…

What does LibreOffice need for the future?

LibreOffice needs to listen to its users again and again. It must remain open source.

Many thanks to Dominique for the support in our community! And LibreOffice will always be free and open source software, so no worries about that 😊

LibreOffice community interview: Robert Cabane, QA project

Robert Cabane

Today we’re talking to Robert Cabane, who helps out in LibreOffice’s Quality Assurance (QA) community:

Tell us a bit about yourself!

I’m now retired (aged 71), living in Bordeaux, France. Formerly mathematics teacher, successively in Paris and Bordeaux, and as such involved in the teaching of computer science (named “informatics” in Europe).

Since my retirement, I have been an active member of the Société Informatique de France. I have also been co-author of some textbooks on mathematics.

In my free time I like to go hiking in the Pyrenées mountains.

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

I like to detect bugs and check for them in Bugzilla! When you encounter something strange using LibreOffice, it’s not immediately clear whether it’s a bug or a feature… so I first look in Ask LibreOffice or the forums.

After that, searching in Bugzilla for a specific bug is a unique experience, because LibreOffice is an enormous piece of software. You have to test various keywords in order to eventually find a more or less corresponding bug description. If the bug is referenced, consider adding useful comments; if it’s not the case, try to propose a new bug, as well-documented as possible.

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

I started as a user with StarOffice 5.2 (1999), simply because I needed a good office suite running under Linux, and I followed with OpenOffice.org and LibreOffice since its beginning.

My experience was excellent with Calc, good with Draw, and more difficult with Writer, essentially because of two reasons: writing mathematics with Writer isn’t as easy as it is with LaTeX, and exchanging documents with people who use Microsoft Word can be very frustrating at times.

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

I think that some activism is still useful at the citizen level: using LibreOffice instead of Microsoft Office is now very common in local, regional and national associations, and should increase for evident reasons. And making donations eligible to tax deductions (as is the case in Germany) would be fantastic!

Big thanks to Robert for all his contributions! Everyone is welcome to join our QA community and help to keep LibreOffice rock-solid.

Community Member Monday: Jean-Francois Nifenecker

Screenshot of TheCAT LibreOffice extension

Today we’re talking to Jean-Francois Nifenecker, who’s working on LibreOffice extensions and macros, and more…

Tell us a bit about yourself!

I’m 68 years old, freshly retired from a job as a French civil servant (local IT department). I’m married and have three children and nine grandchildren.

I’ve been living in Bordeaux for 35 years now, and I like going to the movie theater, walking, reading and… computing 😄

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

I’ve been a long time user of OpenOffice.org (since v.1.1.1 in 2005), and then naturally, LibreOffice. Since the beginning, I’ve wanted to learn about the tools I’m using and document them. This is why I’ve written a batch of user docs for OpenOffice.org (14 docs, still available on their web pages).

The user side of the documentation is still something I’m thinking of. But, in parallel, I’ve created a (very) small business to help a friend of mine, regarding migration and training from other office suites to LibreOffice. And then, as I have a programming background (mainly in Pascal and Object Pascal), I have been working on the macro side. This is a part of my business since migrating macros from Excel to Calc can be a chore. Naturally, I’ve spent “some” time into extensions creation (like the one pictured above).

I’ve written a set of reference cards (in French and in English) about BASIC macros programming, that Olivier was kind enough to publish on the extensions site 😄

LibreOffice reference card header

Thus, programming macros and extensions is my main current activity in LibreOffice.
I’ve written a set of “articles” in English for my own use until now, which I grouped under “The LibreOffice Macros Corner” title, with the aim to publish them sometime, when I’ve got time/desire enough to set a website (which is not the case).

Also I’ve got a book (currently in French) on my plate about extension creation. It is a long time project, started two-to-three years ago, which still requires much work. I think such a resource is missing and might help programmers to go one step further.

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

I actually saw the project creation after Oracle took over Sun but had not much time to participate when I was still active (I guess I’m still active, but well…).

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

My only “skill” is with documentation and macros programming, so I’d continue on this route.

As a heavy user of Writer (among others 😉), I’m missing a few features, but it seems that there aren’t enough resources to satisfy my demands: pages styles inheritance, real table styles instead of a fake one which is more annoying than helping are my main gripes 😄
Unfortunately I can’t help the developers here 🙁

Thanks a lot to Jean-Francois Nifenecker for his contributions and support! And if anyone else wants the features he mentioned, get involved and give us a hand, or consider funding a developer. Then everyone benefits!