Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi there,

Good to see you are motivated to hack on LibreOffice for Google Summer
of Code. In our selection process we want students to have fixed a
non-trivial easy hack or bug. And the best way for you to start is to
dive into the code right now. Starting to work on the area that interest
you can only help you.

First steps:
  * Get the whole thing build
  * Pick a project idea or easy hack
  * Read the code and start with small patches.
  * Submit your patches for review.

I hope this helps,
--
Cedric

On Fri, 2014-01-24 at 02:12 +0530, GAURAV Agrawal wrote:
Hello,


I am a 2nd year computer science engineering student and I want to
take part in Gsoc 2014 by contributing to LibreOffice. I have browsed
through the LibreOffice list of ideas for Gsoc 2014.


I have some programming experience with C++ and am really keen to
apply this knowledge to some practical application
.
I don't have any prior application development experience but I am
willing to be a part of it.Please,if anybody could help me to start
contributing to LibreOffice and guide me about the chances of becoming
a potential contender for bagging a LibreOffice project in Gsoc 2014
and steps to do so,that would be really appreciated .


Thanks


Gaurav Agrawal
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.