Development/GSoC/2014

From The Document Foundation Wiki
Jump to: navigation, search

Welcome to LibreOffice Google Summer of Code 2014!

Introduction

Want to apply for the LibreOffice project in 2014? Read the #Important dates and #How to apply sections below!

Important dates

See the timeline on GSoC FAQ. In short:

  • February 14th - last day to submit LibreOffice application for GSoC 2014
  • March 21st - student application deadline
  • April 18th - all students must be coupled with a mentor
  • April 21st - list of accepted students is published
  • May 19th - the coding start
  • June 27th - the mid term evaluation deadline
  • August 18th - pencils down
  • August 25th - final results 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:

  • 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 the Development page for more infos on this.
  • 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.

Handy Tips

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

Accepted Students

Student Title Mentor Who presents at Annual Conference?
J Random Hacker (Example row in table) Michael Meeks Mr. Hacker