<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi René, The reference to GitLab was given for info only, just to show the progress of the project. 1. The DocFiles directory is there only to collect useful info for the participants to the development. It is not part of what will be integrated in LO. 2. The QA directory is, for the time being, for internal unit tests only. 3. All integrated files will be licensed under MPL 2.0 or LGPL 3+. Read the individual __License.xba files. 4. The (root) LICENSE file will be updated (on GitLab) accordingly. Note that it is not part of the LO sources. Added files are in (and only in) the SFDatabases, SFDialogs, SFDocuments, ScriptForge, po and python directories. The integration within LO will be done manually. The Help directory will be integrated in a later step. Concretely, in the short-term: - ScriptForge, SFDatabases, SFDialogs and SFDocuments will come under wizards/source - po and python will come under wizards/source/ScriptForge - impacted: Repository.mk desktop/CppunitTest_desktop_lib.mk scp2/source/ooo/directory_ooo.scp wizards/Module_wizards.mk: addition of 4 packages - addition of next files: wizards/Package_scriptforge.mk wizards/Package_sfdatabases.mk wizards/Package_sfdialogs.mk wizards/Package_sfdocuments.mk If you still have questions do not hesitate. Thanks a lot for your remarks. Jean-Pierre <div class="moz-cite-prefix">Le 31/10/20 à 09:52, Rene Engelhard a écrit : </div> <blockquote type="cite" cite="mid:757b5208-41f1-ec77-a067-7ba7fc74e5fd@debian.org"> <pre class="moz-quote-pre" wrap=""> Am 30.10.20 um 14:33 schrieb Jean-Pierre Ledure: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">Hi, during the coming week, the ScriptForge library (read below) will be integrated in the master branch of LO. It consists in a significant number of new (Basic, Python, text) files and a few new directories. With also an impact on a number of .mk files. The building process has been tested already on my local repo and should not cause any inconvenience, ... but, you never know ... </pre> </blockquote> <pre class="moz-quote-pre" wrap="">It should support to use a separately packaged ScriptForge (even if it's only data) by specifying where it is in some config. Since it's a separate project it should be packaged separately. That said I noticed a few things: - which version? There is no release and I hope you won't add some "random" git snapshot? - you include some non-free files in DocFiles. e.g. "GeneralPurposeProgrammingLanguages.zip" which contains the VBA Specification... - what is the license? - LICENSE contains GPL 3, python/ScriptForgeHelper.py explicitely states MPL 2.0 or LGPL 3+ So what is deductible from it right now (and which I need to document when packaging this either standalone or in LibreOffice itself) is: "anything is GPL 3 except python/ScriptForgeHelper.py". Correct? Regards, Rene _______________________________________________ LibreOffice mailing list <a class="moz-txt-link-abbreviated" href="mailto:LibreOffice@lists.freedesktop.org">LibreOffice@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/libreoffice">https://lists.freedesktop.org/mailman/listinfo/libreoffice</a> </pre> </blockquote> </body> </html>