LibreOffice Google Summer of Code

From The Document Foundation Wiki
Jump to: navigation, search

LibreOffice has participated in the Google Summer of Code (GSoC) Mentoring Program for many years.


LibreOffice intends to apply as an organization for Google Summer of Code. The GSoC program helps students to dive into the open source world and we hope to match challenging projects with bright students this summer. Please refer to the GSoC Ideas page for projects ideas.

  • Have some interesting project idea? You can add some exciting project idea to the GSoC Ideas, but don't forget that students only have a full-time summer to work on it and that they may need some time to get up to speed.
  • Want to apply for a project? Go to the GSoC page for the current year.

Current Year: 2017


Project ideas can be found on the GSoC Ideas page.

By Year

Successfully Implemented Ideas

see Development/GSoC/Successfully Implemented Ideas

2017 GSoC application

Organization Profile

Public Profile

Website URL


Free Office Suite, Fun Project, Fantastic People

Upload Logo


Primary Open Source License GNU Lesser General Public License v3 (LGPLv3)

Organization Category End User Applications

Technology Tags

C++ Python Java

Topic Tags

office suite cloud big project android ios windows linux osx

Ideas List


Short Description

LibreOffice is a lively and diverse community, delivering a full-featured cross-platform office suite. We value new contributors, just as we prize Open Source and Open Standards.

Long Description

LibreOffice is a modern Free & Open Source Office suite, one of the largest open source projects, and used by millions of users worldwide. LibreOffice is compatible with many file formats like Microsoft® Word, Excel, PowerPoint and Publisher. At its heart though, LibreOffice is built around an open standard, the OpenDocument Format, as its native file format.

LibreOffice is developed by users who, just like you, believe in the principles of Free Software and in sharing their work with the world in non-restrictive ways. The development of LibreOffice is supported by The Document Foundation which provides the infrastructure for the project.

We believe that users should have the freedom to run, copy, distribute, study, change and improve the software that we distribute. While we do offer no-cost downloads of the LibreOffice suite of programs, Free Software is first and foremost a matter of liberty, not price. We campaign for these freedoms because we believe that everyone deserves them.

Though the members of our community hail from many different backgrounds, we all value personal choice and transparency, which translates practically into wider compatibility, more utility, and no end-user lock-in to a single product. We believe that Free Software can provide better-quality, higher-reliability, increased-security, and greater-flexibility than proprietary alternatives. LibreOffice is a large project (approx. 6MLOC), which makes it interestingly complex, but at the same time, provides a place for all sorts of contribution & skills.

The community behind LibreOffice is the heart of the project, without which we would not have the resources to continue developing our software. The passion and drive that every individual brings to the community results in collaborative development that often exceeds our own expectations. With tons of different roles in the project, we invite everyone to join us in our work and help us to make LibreOffice known, prosper, and accessible to all.


Application Instructions

First you should have a look at the Google Summer of Code FAQ and GSoC Student Guide. We will require the following points in any application:

  • Present yourself
  • Prove that you want to get involved into LibreOffice
  • Explain what you want to achieve
  • How do you plan to achieve it?
  • Why should we choose you?

Please find more details on the application process in our wiki

Remark, in order to ensure you have aquinted yourself with the project, you need to have solved at least one non-trivial easyHack.

Proposal Tags

C++ Python Java new idea easyHack ref

Contact Methods

IRC Channel

Mailing List

General Email


Google+ URL (optional)

Twitter URL (optional)

Blog URL (optional)


Why does your org want to participate in Google Summer of Code?

GSoC attract a lot of students of whom some can be motivated to be long term committers. An mature project like LibreOffice, need a mixture of old and new developers, hence GSoC is very important for our future. For the student, being part of a large well known project like LibreOffice is a big plus on their CVs, something we take very seriously. GSoC is the major opertunity for students around the world to be an active part of OpenSource, and we want to help making it a combined success.

GSoC is an important program, because it provides a possibility to mentor students intensively over a relative long period of time. The Student gets more experience, while the project get tasks done, that would be harder to do, but pure volunteers. GSoC provides a platform, that connects students with openSource projects, LibreOffice interact with the students after GSoC, to e.g. provide developer days in universities.

How many potential mentors have agreed to mentor this year?


How will you keep mentors engaged with their students?

We use mail and IRC as the primary communication channels, with an exceptional g++ hangout when needed. In order to monitor the overall process, we have a weekly steering meeting, where GSoC are discussed in order for detecting problems before they become real problems. Each student will have two mentors to avoid problems of disappearing mentors (even if only during the holidays time). Furthermore the GSoC admins (3) keeps an oversight throughout the project period.

How will you help your students stay on schedule to complete their projects?

Our mentors are typically people, who are present on our IRC channels and mail on a daily basis and have therefore sufficient capacity to adhere to the students schedules. Our GSoC administrators (some are also mentors) will follow the progress of each sub-project at a high level. We use Gerrit for patch management, and with that it is easy to monitor the progress in work.

In order to be selected, the students need to accomplish an easy programming task or fix any easy bug from LibreOffice bugzilla. This requires them to build and start looking at the code, this gives the student more confidence in the task ahead and our mentors a chance to look at how the student work.

All students will be required to submit report their progress every week on the libreoffice development mailing-list and submit/update a patch on gerrit every week. This will help to spot the difficulties before the student is actually lost. The report doesn't need to be long if the patch clearly show work is being done.

How will you get your students involved in your community during GSoC?

The students are, from before applying to GSoC, being welcomed as part of our mentoring program. In the mentoring program, we encourage the students to participate in discussions on IRC and mail. Our mentors will often, ask the students to present their ideas to the community and thus get involved. In our opinion students need to do more than just write code, they need to interact with the community by propoising solutions and modity them until we have a community consensus. The interaction will ensure that students become part of the "team".

How will you keep students involved with your community after GSoC?

We have a mentoring program in place, with the purpose an guiding new contributors into becomming full committers. The GSoC students will be (since most of them are new) will be part of that program. We not only help new contributors becomming part of the community, we also monitor progress, and actively try to keep the motivation high. We believe an open and active community is one of the best assets in keeping contributors. We will before, during and after GSoC keep a personal contact with the students making them be a part of the community.

This year our community are reaching out to universities, using the GSoC students as our advocates, providing "developer days", where the mentors will be present.

Has your org been accepted as a mentoring org in Google Summer of Code before?


Which years did your org participate in GSoC?

2016 2015 2014 2013 2012 2011 2010

What is your success/fail rate per year?

2011 7/7 2012 ?/? 2013 ?/? 2014 ?/? 2015 12/1 2016 11/1

If your org has applied for GSoC before but not been accepted, select the years:

If you are a new organization to GSoC, is there a Google employee or previously participating organization who will vouch for you? If so, please enter their name, contact email, and relationship to your organization. (optional)

Are you part of a foundation/umbrella organization?


What year was your project started?


Anything else we should know (optional)?

LibreOffice is a fork of and the Go-oo project migrated to LibreOffice. LibreOffice in itself only participated from 2011 GSoC, but:

  • did in 2005, 2006 and 2007
  • and Go-Oo did in 2009 and 2010