On Sat, Jun 22, 2013 at 10:11 AM, Sonakshi Nathani <
sonakshinathani@gmail.com> wrote:
I really want to contribute for libreoffice. For that I went through
https://wiki.documentfoundation.org/Development/Easy_Hacks ,but i m
really confused from where to begin and how to begin. If anyone can help ?
The page https://wiki.documentfoundation.org/Development has the "building"
(source code compilation) instructions for Linux, OS/X or Windows.
Your first step is to setup your computer in order to build LibreOffice
from source code. The first compilation may take a few hours, depending on
the computer. You must go through this, and verify that the
freshly-compiled LibreOffice works. When you then make small changes to the
source code, the new compilation will be much faster, such as a few minutes
or less.
Then, if you are not already familiar with the source code management tool
called 'git', try for example http://try.github.io/
'Git' is very important, because you can change a bit of code, compile
again, and if it does not work, you can easily go back to the working state
you had in the beginning. If the change works, 'Git' will help you to
generate the changes/patch to send here.
There are many bug reports that require just a few lines of code, but they
are still pending because it takes some effort to set up the build
environment and compile for each case. If you go through the general
Bugzilla list or the EasyHacks list, you can find several of them.
Simos
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.