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


I don't find a way to comment directly at <https://amantke.de/2018/08/29/some-hints-on-publishing-extensions/>, so moving that here. Quoting that blog post:

[...]
But without a proper license the Extension it is not appropriate to publish the Extension on the 
LibreOffice Extensions website.

But it is not a very difficult task to add such a license information to the Extension. Just add a 
text file with the license to the Extension (zipped) container (preferably in a subfolder) and 
update the description.xml with the following xml-tag:

<registration>
<simple-license accept-by=”admin” suppress-on-update=”true” >
<license-text xlink:href=”<relative link to the license file>”
lang=”en” />
</simple-license>
</registration>

The description.xml simple-license element is about asking the user to actively accept a license before installing/using the extension. This is awkward UX and I guess that many extensions do not want to bother users with click-through license bla bla.

I don't think that it is a good idea to tie the question of whether an extension is suitably licensed for publishing on LO's extension site to the presence of such a simple-license element.

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.