On Montag, 19. Dezember 2022 23:34:11 CET Simon Redman wrote:
> But my view don't matter, what matters is what happens in court, in the
> event anyone ever accuses KDE of violating license terms. As I am not
> qualified to expose KDE to any additional risk, is there a policy (or
> accepted preceden
Oops, I somehow misunderstood the question as being about iOS but it's
actually Android. Do you work on both? Your name may be what confused me.
My reply should still be applicable anyway, other than the specific examples
and references to Apple :)
> El 20 dic. 2022, a la(s) 01:41, Nicolás Alv
(This is "as I understand it", not legal advice, I am not a lawyer, etc etc)
The system library clause is, for example, what lets KDE Connect (under the
GPL) link to the iOS system frameworks (under a proprietary license).
System libraries have nothing to do with the Apache situation. GPLv2 and
Hi Andrius,
Thanks for your input.
That is the textbook answer, but doesn't actually fit this case. GPLv3 is only
compatible with Apache because it has an exclusion for system libraries, but
KDE Connect is an Android app so there is no concept of system libraries.
It doesn't get to the core of
Hi,
Quick check seems to indicate that KDE Connect license is:
*GPL-2.0-only* OR GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
Apache v2 licensed code is not compatible with GPL-2.0-only but
is compatible with GPLv3. So by combining KDE Conenct with
that library you lose right to redistribute the
KDE Connect has had this PR languishing for a couple of years, with a
question I am not able to answer.
https://invent.kde.org/network/kdeconnect-android/-/merge_requests/192
The author has added a (very useful) library, which happens to be
licensed under the Apache v2 license.
KDE Connect co
