Extending the license policy to include Apache-2.0
Aditya Mehra
aix.m at outlook.com
Fri Sep 17 03:54:48 BST 2021
+ 1
some Bigscreen python-based subprojects interfacing with Mycroft hosted on invent are Apache licensed as Apache is widely accepted in the Mycroft community as the go to license for any contributions.
________________________________
From: kde-community <kde-community-bounces at kde.org> on behalf of Alexander Potashev <aspotashev at gmail.com>
Sent: Thursday, September 16, 2021 5:12 AM
To: informing about and discussing non-technical community topics <kde-community at kde.org>
Subject: Extending the license policy to include Apache-2.0
Hi,
Parts of https://invent.kde.org/websites/aether-sass/ are licensed
under Apache License 2.0. This disagrees with the KDE licensing
policy.
Considering Apache-2.0 is similar to MIT, I don't see why it shouldn't
be allowed by the policy. Is anyone aware of past discussions of the
KDE licensing policy and reasoning behind this fact?
The proposed addition to the policy section of https://community.kde.org/
Policies/Licensing_Policy would be:
"""
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:
...
[new bullet point] * Apache-2.0: Apache License 2.0 as listed below.
"""
What do you think?
--
Alexander Potashev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20210917/f33a0b55/attachment.htm>
More information about the kde-community
mailing list