Development/GSoC/2018

    From The Document Foundation Wiki

    TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate

    Welcome to LibreOffice Google Summer of Code 2018!

    Introduction

    Want to apply for the LibreOffice project in 2018? Read the #Important dates and #How to apply sections below! The list with proposed GSoC projects including potential mentors can be found here.

    Preamble

    LibreOffice has been approved as an organization for Google Summer of Code 2018. This program helps students to dive into the open source world and we hope to work on great projects with great 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 student only have a full-time summer to work on it and that they may need some time to get up to speed.

    Important dates

    See the How it works GSoC page and the detailed GSoC time line. In short (bold items are LibreOffice project deadlines):

    Start Finish Origin Description
    done GSoC submit LibreOffice application as an organisation for GSoC 2018
    March 12 GSoC Students ask questions and receive feedback to craft their proposals
    March 12 March 27 GSoC Students submit their draft proposals through the GSoC website by March 27, 2018 16:00 UTC (18:00 CEST)
    March 27 April 8 GSoC Review of proposals
    March 26 April 8 LibreOffice Control submitted EasyHacks
    March 31 March 31 LibreOffice Deadline for submission of the mandatory EasyHack
    April 7 April 7 LibreOffice Deadline for merge (accept) of the mandatory EasyHack
    April 9 April 9 GSoC 16:00 UTC: last day to submit slot requests
    April 10 April 10 GSoC 16:00 UTC: slot allocations announced by Google
    April 10 April 17 GSoC Select proposals and confirm mentors by April 17, 16:00 UTC
    April 17 April 23 GSoC Google Program Admins perform additional review of student eligibility
    April 23 April 23 GSoC Accepted projects/students are announced
    April 23 May 14 GSoC Community bonding period
    May 13 May 13 GSoC Last day to report inactive students
    May 14 GSoC Coding begins
    June 11 June 15 GSoC First evaluations, students and mentors
    July 9 July 13 GSoC Second evaluations, students and mentors
    August 6 GSoC Pens down, wrap up
    August 6 August 14 GSoC Students Submit Code and Final Evaluations
    August 14 August 21 GSoC Mentors Submit Final Evaluations
    August 21 GSoC Students passing GSoC 2018 are announced

    How to apply

    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:

    Remember to refer to the Gerrit patches you have submitted.


    • Prove that you want to get involved into LibreOffice. In order to check this we will require students to complete one of the Easy programming tasks on the Easy Hacks page (or part of one if that EasyHack is a selection of separate tasks), though the dead-line for this isn't hard but needs to be somewhere before the end of the selection process. This means that each student who wants to have chances to be picked for a LibreOffice project will need to build the whole application, fix a bug and submit the patch to the development mailing list. See GetInvolved for help on getting started.


    Please remark, remember to compile and test your patch locally before submitting. Submitting a patch that does not compile or fail the automated tests, is seen as lack of interest in getting seriously involved.


    • Explain what you want to achieve. Provide detailed informations on the project you want to work on and the use cases. The more precise your description is, the more it will show us that you investigated the area and though about it properly before submitting. The best is to base your project on one of our Ideas that come complete with friendly mentors to help you. You may have some nice project ideas, but make sure that someone will be able to mentor your project and knows that part of the code well enough.
    • How do you plan to achieve it?. Provide us the following:
      • An estimated schedule for the summer (including any potential conflicts you could have like courses, exams...)
      • Technical details on how you want to implement it. The more sensible details you provide the easier it will be for us to check that you understood the problem and difficulty
    • Why should we choose you?. Give us all the reasons for choosing you. Any past open source hacking is interesting us as well as your hacking and socializing skills.

    If you're looking for further inspirations on how to write a successful application, please again be refer to the excellent GSoC student guide (here is an actual example).

    Accepted Students

    (Students whose application is accepted to GSoC 2018)

    Student Title Mentor Who presents in Tirana
    Nickson Thanda 100 paper cuts Samuel Mehrbrodt, Muhammet Kara
    Shobhan Mandal Add Support for Python in LOEclipse Plugin Samuel Mehrbrodt, Bjoern Michaelsen
    Saurav Chirania Adding a DSL to the UI testing and improving the generated log file Xisco Fauli, Markus Mohrhard
    Vikas Mahato Implement interface for external data source import into Calc erAck, Kohei Yoshida, Markus Mohrhard
    Kshitij Pathania Improvements to Notebookbar Szymon Kłos, Jan Holesovsky
    Manuj Vashist Interface for External Data source import in Calc erAck, Kohei Yoshida, Markus Mohrhard
    Muammer Mert Tümer LibreOffice Android Viewer Tomaž Vajngerl, Miklos Vajna
    Hrishabh Rajput Listbox separate read values from input values Caolán McNamara, LibreOffice Base
    Daniel Silva Revamp Print Dialog Thorsten Behrens, Bubli
    Ekansh Jha SmartArt Editing in Impress Thorsten Behrens, Jan Holesovsky

    Handy Tips

    There's some useful information for Students and for Mentors here:


    2018 GSoC application

    Organization Profile

    Public Profile

    Website URL https://www.libreoffice.org


    Tagline

    LibreOffice is a free and open source office suite.


    Upload Logo

    Logo


    Primary Open Source License Mozilla Public License 2.0 (MPLv2)


    Organization Category End User Applications


    Technology Tags

    C++ Python Java


    Topic Tags

    office suite android end user application desktop application


    Ideas List

    https://wiki.documentfoundation.org/Development/GSoC/Ideas

    Descriptions

    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.

    Proposals

    Application Instructions

    First, please present yourself. Since we don't know you we want to know some bits like your name, education, email address and nickname on the #libreoffice-dev IRC channel at freenode.net. Please subscribe to the LibreOffice developer list and write an email to the list.

    We will require students to complete one of the easy programming tasks on the "Easy Hacks" page (or part of one if that EasyHack is a selection of separate tasks), though the dead-line for this isn't hard but needs to be somewhere before the end of the selection process. This means that each student who wants to have chances to be picked for a LibreOffice project will need to build the whole application, fix a bug and submit the patch to the development mailing list.

    Explain what you want to achieve. Provide detailed informations on the project you want to work on and the use cases. The more precise your description is, the more it will show us that you investigated the area and though about it properly before submitting. The best is to base your project on one of our Ideas that come complete with friendly mentors to help you. You may have some nice project ideas, but make sure that someone will be able to mentor your project and knows that part of the code well enough.

    Problems that can not be resolved on our public developer mailing list or problems containing privacy relevant topics can also be sent to our mentoring@documentfoundation.org address.

    Proposal Tags

    C++ Python Java new idea online writer calc impress UX

    Contact Methods

    IRC Channel https://wiki.documentfoundation.org/Website/IRC


    Mailing List https://wiki.documentfoundation.org/Development/Mailing_List


    General Email libreoffice@lists.freedesktop.org

    Links

    Google+ URL (optional)

    https://plus.google.com/+libreoffice


    Twitter URL (optional)

    https://twitter.com/libreoffice


    Blog URL (optional)

    https://blog.documentfoundation.org/


    Application

    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 opportunity 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?

    16-20


    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 at least 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. Many of the mentors are employed by companies for their work on LibreOffice and therefore are expected to be available at least during the week.


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

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


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

    Yes


    Which years did your org participate in GSoC?

    2017 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 2017 9/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?

    No


    What year was your project started?

    2010

    Where does your source code live?

    https://www.libreoffice.org/about-us/source-code/


    Anything else we should know (optional)?

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

    • OpenOffice.org did in 2005, 2006 and 2007
    • and Go-Oo did in 2009 and 2010
    Retrieved from "https://wiki.documentfoundation.org/index.php?title=Development/GSoC/2018&oldid=168144"