On Dienstag, 18. August 2020 12:34:42 CEST Harald Sitter wrote:
[...]
> > Ouch, yes, the obvious choice, no idea why I did not see that by myself :)
> > Yes, SPDX expressions should be the obvious way to go IMO. For the
> > questions: - for libraries, I agree that the target name should be
> > easi
On Mon, Aug 17, 2020 at 8:24 PM Andreas Cord-Landwehr
wrote:
>
> Thanks! I will answer inline:
>
> On Montag, 17. August 2020 17:47:40 CEST Harald Sitter wrote:
> [...]
> > > **First question:** Shall we only list ONE or ALL licenses, same for the
> > > license information overview that should be
Thanks! I will answer inline:
On Montag, 17. August 2020 17:47:40 CEST Harald Sitter wrote:
[...]
> > **First question:** Shall we only list ONE or ALL licenses, same for the
> > license information overview that should be on api.kde.org?
>
> The primary use would be api.kde.org, no? A third part
On Mon, Aug 17, 2020 at 2:16 PM Andreas Cord-Landwehr
wrote:
>
> Hi, I am currently looking into extending our metainfo.yaml files to provide
> information about the outbound licenses of the artefacts that are provided by
> a framework. Here a few examples:
>
> Attica: Provides libattica, which is
Hi, I am currently looking into extending our metainfo.yaml files to provide
information about the outbound licenses of the artefacts that are provided by
a framework. Here a few examples:
Attica: Provides libattica, which is legally OK to be used as LGPL-2.1 or
LGPL-3.0 (and of course also as