Category: Development

Earlier in the week we talked to Jan Iversen who is mentoring new contributors to the development team. Let’s now look at some of the people involved, statistics from recent months, and the tools used by developers in their daily work.

Who’s who

As with other large free and open source software projects, LibreOffice developers come from a variety of backgrounds: some are paid to work on the code by companies that use or offer support for LibreOffice; others contribute in their spare time because they enjoy programming and working with the community. If you’ve looking to build a career as a software developer, working on a well-known open source project can provide you with great experience, and is something to put on your CV.

Because the LibreOffice codebase is quite large, most developers focus on certain areas. Some work on specific components of the suite like Calc or Writer, whereas others concentrate on the user interface or improving overall performance. Here is a list of “friendly experts” who are well versed in the code in specific areas, and who can help with questions or problems. But please remember: these are very busy people, who do not always have time to answer beginners’ questions, especially on IRC. The best practice is to send an email to our dev list, which will be seen by all developers including Jan.

Running the numbers

So who is committing code, and how often? Here’s a break-down of commits in the past 12 months:

Some other interesting statistics:

• In the last 12 months, 282 different contributors had patches merged
• There are 253 Easy Hacks ready for contributors (new and existing)
• The Engineering Steering Committee (aka ESC) publishes a list of top 5 contributors every week on our dev mailing list – a lot of companies look at these emails, so being on that list is a plus if you’re searching for a job
• Development mentor Jan does 50 reviews per week for patches from contributors

Finding the right tools

As mentioned, most of LibreOffice’s source code is C++. Developers use their own choice of editors and development environments to work on the code. The version control system used by LibreOffice developers is Git, while Gerrit is used for review.

For a list of all the tools available to developers, see devcentral.libreoffice.org. Some of the most notable include:

• Opengrok, which provides a friendly and attractive way to browse the source code
• Jenkins, which provides CI (continuous integration): every patch which is submitted is built and tested automatically before being merged into the master code branch, to keep master stable
• Tinderbox, which supports a lot of different setups, and tests regularly (several times a day) that master can build in this special version
• And Gerrit, where patches end up. This is the system where we review patches before merging to master

So now you have an overview of the development community and the tools that they use – stay tuned for Friday’s post, where we show you how to get involved with Easy Hacks!

Last week we looked at the documentation team’s role in the LibreOffice project, and this week we move on to development. As you’d expect, the development team is responsible for updating and maintaining LibreOffice’s source code – adding new features, fixing bugs, and making sure that the suite builds correctly across various operating systems.

Development may seem like the most daunting sub-project in LibreOffice, but there are many ways to get involved, even for less-experienced programmers or those with just a couple of spare hours every week. We have “Easy Hacks” to get new contributors on board (more on those later in the week), and we have a dedicated mentor who helps first-time developers explore the source code, build it, and create their first patches.

His name is Jan Iversen, and we asked him about his role and how he helps newcomers…

What is your role in the development team?

My role is to mentor new contributors, and in general help the development community grow. I often act as a intermediary between new people and core developers, to save time for the core developers. To help the community I am also a “part-time” release engineer and I help the infrastructure team as well.

What does your typical workday look like?

I start every morning by looking at new patches in Gerrit from new contributors, comment on them and if they look good, assign a core developer to make the review. I also control the state of bugs.documentfoundation.org with regards to our Easy Hacks, control new ones, and check comments on existing ones.

On average there are 5-10 mails in my inbox, mostly from contributors but also more and more from the rest of the community.

The rest of my workday goes with the bigger tasks, like:

• Rewriting big parts of the development wiki
• Being available on IRC (I am there 24/7 as @janIV – or more correctly, messages are stored when I sleep
• Rewriting our Easy Hacks to make them more understandable

As I live in Spain, I also work to get the Spanish community up and running.

How many developers are active in a typical week?

We have a nice page of stats for that.

In a typical day, I guess there are about 20 different people active on IRC and 5 on email. We are about 10 people who, as a person told me, have a IRC client seemingly built-in to their brains! And the others are people popping in for a question.

It is very clear that IRC is for the more hard-core developers. New people especially use social media a lot more, so I am working on getting social media interconnected with IRC.

What’s the biggest success so far, and the biggest challenge?

My biggest success was Google Summer of Code (GSoC), where our community managed to get the largest number of applicants to date. Google sadly enough only awarded us 12 seats, so we had to select the projects carefully.

My biggest challenge, is and will be for some time, to change the way we communicate, to a style more acceptable for especially students. This must be done as a evolution, not a revolution, in order not to break the existing community.

What sort of help are you looking for?

LibreOffice is very much C++, so people who know C++ and want to learn how to work with a big project are very much sought after.

But in reality, we have Easy Hacks for a lot of programming languages, so everybody is welcome. One of the people I mentored started by telling me that he was a newbie in programming. It made me very happy when he lately was given committer status, so people tend to grow with the community.

Local community building is my theme for 2017: having small groups of developers that help each other is something I would like to see, and then we will help such groups, by having mentors ready to help them. Also, I have – among others – created a step-by-step guide explaining how to get from you first contact with the community to have successfully submitted your first patch: see this page.

Thanks Jan. Later in the week we’ll look at some stats from the development team, see what tools are used, and show you how to get involved. You could even be awarded a shiny certificate like the one below when your first code patch is accepted…

The Document Foundation is happy to share with the community the opportunity represented by Prototypefund (http://codefor.de/blog/prototype-fund), an excellent project for freelance developers based in Germany.

TDF Board of Directors encourages all hackers with the necessary credentials and interested in improving either LibreOffice or the Document Liberation Project to apply for the fund. Approved projects will be supported by the LibreOffice development community, which will provide the mentoring resources to achieve the objective.

This is a list of potential projects, which will be very helpful both for LibreOffice users and for the broad scope outlined by Prototypefund:

1. Develop a LibreOffice Calc import filter from public administration sources, to allow citizen to process and analyze data themselves. Such an import filter would allow to easily create content for publication.
2. Develop a digital tool based on LibreOffice, to create, share and use (open) data, for data visualization and storytelling, social engagement, transparency and citizen participation. An example project would be to create a filter that export diagrams in Calc to d3js for publication on the web.
3. Develop an “open data browser” – most likely as an extension – capable of importing data made available at: https://offenedaten.de/dataset into LibreOffice Calc or Base.
4. Allow LibreOffice to read/process and render basic geographic data from OSM using Calc or Draw.

These are just examples, which can be used to look at Prototypefund in a creative way, to write the project (according to the website, one page should be enough to apply).

The Document Foundation is happy to help the interested developers with their pitch related to the development of LibreOffice.