Hi,
That's good news. The next step for you is to pick an easyHack to tackle on. You can choose any
that's listed here:
https://wiki.documentfoundation.org/Development/EasyHacks/by_Required_Skill
<https://wiki.documentfoundation.org/Development/EasyHacks/by_Required_Skill>
Or even better, I have a recommendation for you:
https://bugs.documentfoundation.org/show_bug.cgi?id=110742
<https://bugs.documentfoundation.org/show_bug.cgi?id=110742>
The way you would go about this is register with Bugzilla, assign the bug to you to signal that
you've started working on it and then proceed. As soon as you have a workable patch you need to
register using Gerrit and submit your patch for review, follow these instructions:
https://wiki.documentfoundation.org/Development/gerrit
<https://wiki.documentfoundation.org/Development/gerrit>
If you get stuck or need further help, you can ask for it using this list, the Bugzilla comments
section or hop on to IRC at freenode.net on channel #libreoffice-dev.
Cheers,
Shinnok
On Sep 7, 2017, at 5:27 PM, namitha.ninan@ssrlabs.com wrote:
Hi Shinnok
As per our previous discussions, I have completed the make with
build-nocheck and it seems to have run without an issue. With this the
build issues appear to have been solved after running
./autogen.sh --without-java --without-doxygen --disable-cve-tests and make
build-nocheck. What would be the ideal procedure to proceed further ?
Regards
Namitha Ninan
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Context
- Re: Report for 09/07/2017 · Shinnok
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.