Hello,
take a look at our wiki:
https://wiki.documentfoundation.org/Main_Page
You have probably seen the GSoC page, there is info about tasks to do at
the top of this page:
https://wiki.documentfoundation.org/Development/Gsoc/Ideas
To prove your skills you can do one of Easy Hacks (I think you should
take something more challenging than fixing cppcheck warnings):
https://wiki.documentfoundation.org/Development/Easy_Hacks
...but better will be asking chosen Idea's mentor (on IRC
#libreoffice-dev channel or by an e-mail) - a potential mentor for
Application Themes is Jan Holesovsky (kendy), as you can see on a
mentioned page.
Best regards,
Łukasz Hryniuk
On 10/03/15 19:36, Siddharth Agrawal wrote:
Hello,
Myself Siddharth Agrawal,an undergraduate 2nd year student(Information
Technology) at IIIT Bhubaneswar,India. I am happy to see Libreoffice
selected as mentoring organisation. I want to contribute Libreoffice
in this summer of code. I want to work on improving Application Themes
of Libreoffice. I have a good experience in C++ and I can
understand codes written by others. I am also interested in Improving
user experience with Gdocs, Onedrive,etc.. Can anyone please guide me
where should I start with or what to do in order to prove my skills?
Regards,
Siddharth 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.