> I'm not familiar with MySQL, but OpenOffice is LGPL, not GPL;
furthermore, OpenOffice is an app, not a framework like Qt. For both of
these reasons I see little or no cause for concern if Sun should change
OpenOffice's license to some other FOSS license. That is, if I want to
write a plugin for OpenOffice using the GPL4, I will have no problem.
if you are really this much concerned about not being able to use
not-yet-existing OSS licenses and about being able to write proprietary
derivate works without a payment, you really should be using a BSD instead
of the linux kernel: Even if there was desire to switch to GPLv3, linux
is still stuck to the GPL v2 until _every_ contributor agreed on
relicensing or alternatively every single line of code from authors who
haven't agreed is removed.
on the other hand you will always be able to use/fork/remix all versions
of Qt with (A)GPLv(2|3) code and link it to any code which uses one of the
licenses mentioned in Qt's GPL exception. Also if you want to use your
code with a newer license you can still dual-license it.
Posted Jun 6, 2008 18:24 UTC (Fri) by kripkenstein (subscriber, #43281)
[Link]
Actually the Linux kernel is close enough to what I want: I can write userspace apps using any
license and run them on the Linux kernel. It's like the LGPL in that respect. That is, only if
I want to extend the kernel itself do I have license issues - which is the same situation with
GTK+, which is LGPL.
In other words, that the Linux kernel stays GPL2 doesn't matter to me, unless I want to extend
the kernel itself. Same as with GTK (which is also GPL2 last I checked, and again, it doesn't
matter unless I extend GTK itself).
This is the reason I prefer GTK and the Linux kernel's approach to licensing over Qt's (for
libraries/frameworks, at least. For normal apps, other licenses might be better).