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


On Sat, Jan 17, 2015 at 1:36 PM,  <varun.vd1994@gmail.com> wrote:
Hello,

I am an undergraduate student and I have relevant skills of C, C++ and Java.
I have developed various projects on Windows Platform. But now I want to
contribute to the open source world.

Sounds great!

Can anyone please help me for getting started with open source. I want to
contribute to the Libre.

Contributors to the project are generally around during the work week,
so that's usually the best time to correspond with people on IRC.
(Mailing lists are, of course, more flexible :-)

Is there anything in particular that you're hoping to work on within
LibreOffice? Often the best way to get started on the development side
is to
- Build LibreOffice
https://wiki.documentfoundation.org/Development/GeneralProgrammingGuidelines
- Find and fix an Easy Hack
https://wiki.documentfoundation.org/Development/Easy_Hacks

Of course there are many different teams in the project, including QA,
Language/Localization, Design, Documentation, etc..., several of which
can benefit from someone with development experience!
https://wiki.documentfoundation.org/Teams

Looking forward for positive response.


Well welcome to the project! We're always happy to have eager, skilled
contributors join us :-)

Cheers,
--R


-- 
Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qubit@libreoffice.org

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.