Re: Releasing a non-KF5 library under MIT License

2021-03-31 Thread Andreas Cord-Landwehr
On Mittwoch, 31. März 2021 01:52:02 CEST Alexander Potashev wrote:
> On Wed, Mar 31, 2021 at 12:54 AM Luigi Toscano  
[...]
> > 4. Source files that are part of a library with a public API which is part
> > of the KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks)
> > must be licensed under:
> > [... licenses, including: ...]
> > 
> >  * MIT: MIT license as listed below.
> > 
> > [...]
> > 
> > 5. Any other source files must be licensed under one of the terms listed
> > under 4) or:
> > [ other licenses]
> 
> Makes sense. Thanks for pointing this out!
> 
> (IOW the licensing policy "KDE Platform" is even tighter and for the
> other projects, and this is great for me!)

Hi, the idea behind this policy is to ensure that code can (somehow) easily be 
moved between KDE projects. Most permissive licenses are completely fine to 
achieve this goal as long as they are compatible with the (L)GPL versions that 
the majority of the code is licensed under. -- This is the case for MIT.

Luckily, as Luigi pointed out, our policy already says that MIT is OK to be 
used :)

Cheers,
Andreas





Re: Releasing a non-KF5 library under MIT License

2021-03-30 Thread Alexander Potashev
On Wed, Mar 31, 2021 at 12:54 AM Luigi Toscano  wrote:
>
> Alexander Potashev ha scritto:
> > The https://community.kde.org/Policies/Licensing_Policy says I can't
> > do this because (according to this policy) the MIT License is only
> > allowed for parts of the "KDE Platform".
>
> Does it? I see:
>
> 4. Source files that are part of a library with a public API which is part of
> the KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks) must be
> licensed under:
> [... licenses, including: ...]
>  * MIT: MIT license as listed below.
> [...]
>
> 5. Any other source files must be licensed under one of the terms listed under
> 4) or:
> [ other licenses]

Makes sense. Thanks for pointing this out!

(IOW the licensing policy "KDE Platform" is even tighter and for the
other projects, and this is great for me!)

-- 
Alexander Potashev


Re: Releasing a non-KF5 library under MIT License

2021-03-30 Thread Luigi Toscano
Alexander Potashev ha scritto:
> Hi,
> 
> I would like to release a Go library under the terms of the MIT
> License and host it at invent.kde.org. The library definitely won't
> fit in KF5 because it has nothing to do with Qt.
> 
> The https://community.kde.org/Policies/Licensing_Policy says I can't
> do this because (according to this policy) the MIT License is only
> allowed for parts of the "KDE Platform". 

Does it? I see:

4. Source files that are part of a library with a public API which is part of
the KDE Platform (kdelibs, kdepimlibs, kde-runtime and KDE Frameworks) must be
licensed under:
[... licenses, including: ...]
 * MIT: MIT license as listed below.
[...]

5. Any other source files must be licensed under one of the terms listed under
4) or:
[ other licenses]


-- 
Luigi


Re: Releasing a non-KF5 library under MIT License

2021-03-30 Thread Jonah Brüchert

Hi Alexander,

To clarify, the MIT licensed files in Kaidan are third party files which 
are not available as libraries and needed to be copied into the Kaidan 
repository, with the exception of the generate-license.py script.


All the actual code of Kaidan is GPL licensed.

Of course this does not mean anything about whether it is generally 
wanted to host MIT-licensed code on KDE Infrastructure.



Am 31.03.21 um 00:16 schrieb Alexander Potashev:

Hi,

I would like to release a Go library under the terms of the MIT
License and host it at invent.kde.org. The library definitely won't
fit in KF5 because it has nothing to do with Qt.

The https://community.kde.org/Policies/Licensing_Policy says I can't
do this because (according to this policy) the MIT License is only
allowed for parts of the "KDE Platform". Can we please review the
policy and stop this discrimination against projects that don't happen
to be part of the "KDE Platform"?


P.S.  It seems like MIT is already used outside of the "KDE Platform":
  - https://invent.kde.org/network/kaidan (at least two files are under 

MIT)

  - http://invent.kde.org/sdk/cutehmi (dual-licensed, including MIT)



OpenPGP_0xA81E075ABEC80A7E.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Releasing a non-KF5 library under MIT License

2021-03-30 Thread Alexander Potashev
Hi,

I would like to release a Go library under the terms of the MIT
License and host it at invent.kde.org. The library definitely won't
fit in KF5 because it has nothing to do with Qt.

The https://community.kde.org/Policies/Licensing_Policy says I can't
do this because (according to this policy) the MIT License is only
allowed for parts of the "KDE Platform". Can we please review the
policy and stop this discrimination against projects that don't happen
to be part of the "KDE Platform"?


P.S.  It seems like MIT is already used outside of the "KDE Platform":
 - https://invent.kde.org/network/kaidan (at least two files are under MIT)
 - http://invent.kde.org/sdk/cutehmi (dual-licensed, including MIT)

-- 
Alexander Potashev