2014-07-02 22:48 GMT+02:00 Norbert Thiebaud <nthiebaud@gmail.com>:
Provided that it is done properly, not overly invasive, and there is
manpower to cater to the port(*), I'd say chances are good we would
accept the patches.
But, I strongly urge you to not wait 'when it is finished'.
A big code dump is very unlikely to be reviewed favorably... I
strongly encourage to get involved early with this dev community, and
seek review of your work early to insure that you are on a track that
will allow a smooth upstreaming.
Will a github fork suffice? I don't want to send my patches upstream
because they are very hacky at the moment and wouldn't get accepted
anyway.
(*) Libreoffice is a fairly active and large project. any port will
need some sustained attention to keep up.
I am aware of that. I am willing to maintain it.
About the issue with UNO I mentioned: it seems it is caused by some
modules not being compiled (I compile them manually one by one now).
I'll try to make full build work and come back with the results.
Regards,
Kacper
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.