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


On 10/10/2018 10:53 PM, Tamás Zolnai wrote:
With this new information I agree that it would be the best to clear the 
licensing and use LLVM in every source file under compilerplugins 
folder. So the question is what is the best way to do that. What is the 
best way to ask every authors for a permission to relicense the code? Do 
we need some kind of short license statement from the authors, similar 
the general LO license statement?

I am not sure that having a subdirectory under core which is licensed 
differently from the rest of the code is good. I imagine a situation 
when one would need a license statement like

   "All of my past & future contributions to LibreOffice may be
    licensed under the MPLv2/LGPLv3+ dual license.

    All my contributions to directory foo may be licensed under the bar
    license.

    All my contributions to directory bar may be licensed ..."

which would become a nightmare. I suppose that if a separate-licensed 
thing is required, then just create a dedicated project, which would be 
external dependency for LibreOffice. Of course, you'd need to get the 
license statements for the existing code (as you discussed).

-- 
Best regards,
Mike Kaganski

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.