Amarok 2 scripting license requirements

[Mark Kretschmann]

On Wed, Sep 30, 2009 at 1:26 AM, Ian Monroe <ian.monroe at gmail.com> wrote:
> On Tue, Sep 29, 2009 at 2:43 PM, Myriam Schweingruber
> <myriam.schweingruber at gmail.com> wrote:
>> Hi Harley,
>>
>> On Tue, Sep 29, 2009 at 20:51, Harley Laue <losinggeneration at gmail.com> wrote:
>>> On, http://amarok.kde.org/wiki/Development/Scripting_HowTo_2.0 it's indicated
>>> that because of Qt 4.4's GPL requirement for derived projects that the script
>>> must also be GPL. This, as many of you know, has changed in Qt 4.5 which
>>> allows LGPL. Should that bottom legal portion be changed now? At the very
>>> least, if it's decided that because Amarok is GPL, and that scripts are
>>> derived work, that they must be GPL too. It should be expressed that because
>>> as such, and not because of Qt's license requirements.
>>
>> First of all, IANAL, but consider the following points:
>>
>> * Amarok still depends on KDE 4.2, hence Qt 4.4
>
> ^^ is why I haven't bothered to change it.
>
> And the fact that they have to use GPL anyways due to running
> in-process in Amarok while using Amarok APIs. Or maybe not sure. :)
> Its all academic until we deprecated Qt 4.4 support.

Yes, it's running in-process with Amarok, which hasn't changed it's
license (still GPL), so I think the Qt licensing change doesn't make a
difference.

And then, I would personally prefer to keep scripts GPL'ed anyway, as
I think it's the more suitable license here. Scripts are not
libraries, after all.

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org