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


Hello,

take a look at our wiki: https://wiki.documentfoundation.org/Development.

First of all, you should be able to build LibreOffice - you can find instructions under the "General 
Programming Guidelines" on the right.

If you're done with it, you can take an Easy Hack from the list (they are tasks for newcomers), 
more info here: https://wiki.documentfoundation.org/Development/Easy_Hacks).

Around your first patch, you should send to this list (libreoffice [at] lists.freedesktop.org) your 
"Contributor statement":
https://wiki.documentfoundation.org/Development/Developers#Example_Statement

If the wiki is not enough, you can always ask here, on IRC (#libreoffice-dev on FreeNode network) or look for 
solution on "The LibreOffice Archives":
http://lists.freedesktop.org/archives/libreoffice/

Hope this will be helpful :-).

Best regards,
Łukasz Hryniuk

On 10.01.2016 13:41, Prasad Ghangal wrote:
Hello everyone,
I am Prasad Ghangal, a BTech student. I really want to contribute in
libreoffice but I have never worked on any open source project before.
I am good at C, C++ and little python.

So can some please help me getting started?

--
Thanks and Regards,
Prasad Ghangal


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