KDE Licensing Policy Updates

Jaroslaw Staniek staniek at kde.org
Tue Sep 20 19:17:57 UTC 2016


On 20 September 2016 at 20:42, Sune Vuorela <nospam at vuorela.dk> wrote:

> On 2016-09-20, Jonathan Riddell <jr at jriddell.org> wrote:
> > Differences:
> > Removed
> > "code may not be copied from Qt into KDE Platform as Qt is LGPL 2.1"
> > Rationale: Qt is now LGPL 3 as well as 2
>
> Qt is not LGPL2.1 in general. As long as we want to be LGPL2.1 compat,
> we can't copy code from Qt.
>

Precision is needed here; ​I can easily copy some Qt project's code ​and
even relicense if I find it useful. I mean the BSD examples.

>
> > Added:
> > ''Applications which are intended to be run on a server'' can be
> > licenced under the GNU AGPL 3.0 or later
> > Rationale: KDE Store code is under AGPL
> > Question: should this be an option or a requirement for server software?
>
> Not a requirement. Just like we don't have copyleft requirements
> anywhere.
>
> And it should also be specific to things on a web server.
>
> For example:
> An imap AGPLv3 server might be a bad thing - there is a way to notify
> the user over teh imap protocol, but it is annoying for users, so it
> should really not be used. (It is the way quota messages and similar
> normally are sent)
>
> > Added:
> > "Content on collaborative edited websites such as wikis must be
> > licensed under the Creative Commons Attribution-Sharealike 4.0
> > International."
>
> Again, I don't think we should force copyleft.
>
> > Changed:
> > "Documentation must be licensed under the Creative Commons
> > Attribution-Sharealike 4.0 International"
>
> Also here. No need to force copyleft.
>
> > Removed:
> > Standalone media files CC 4.. "This does not apply to icons or
> > anything which is likely to be mixed with content under our normal
> > (GPL etc) licences."
> > Rationale: CC 4 is compatible with GPL 3 which is the licence of
> > Breeze icons anyway.
>
> I want my icons licensed under the same terms as my application. Even
> when my application is more liberal licensed than GPLv3.
>

​This. ​

​If I have icons that are part of my LGPL framework, I don't want ​my icons
to be viral making the framework GPL and thus severly self-limited. The
same goes for icons in LGPL apps (yes, LGPL is good for modular apps that
happen to be a source of frameworks).

I see a similar issue with widget styles such as Breeze; their viral GPL
affects apps, libs or plugins that choose to include them. For _nobody's_
benefit.

I see no need to be more paranoiac when dealing with ​friends than it's
needed.

-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20160920/4a7e721c/attachment.html>


More information about the kde-community mailing list