Peter Kovacs wrote:> Currently you have to download the extention in
order to see the license.
With OO 3.3 I have seen that you have to add the license in the extention
description.
You have to distinguish between an extension and a release. The same
extension can have different releases with different licenses (like,
some extensions released as "GPLv2 or later" became "GPLv3 or later"
once GPLv3 was published).
Example of an extension page (the Italian dictionary I maintain):
https://extensions.openoffice.org/en/project/italian-dictionary-thesaurus-hyphenation-patterns
(note: there seems to be a bug; the page used to contain download
statistics but they are not shown now; this is possibly due to the new
SourceForge counters)
Example of a release page (here is where license info would go):
https://extensions.openoffice.org/en/projectrelease/italian-dictionary-thesaurus-hyphenation-patterns-20160210
I wonder if we can read the extention description and use that for the
extention page.
It could help to clarify the user before downloading which condition he is
expecting to agree to.
Plus we could maybe add search functionality based on license information.
It looks like you've never created or uploaded an OXT file: you may want
to create one if you want to play with these concepts. The site does the
processing, but indeed the license is not shown. And it wouldn't be
useful for indexing as it is free text or link (if I remember
correctly). So you can write "GPL3", "GPL 3", "GPLv3", "GPL version 3"
or any link to the GPLv3 and it would be classified differently.
But showing the license info would be useful and probably feasible.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
