Re: [Lxde-list] LXDE-Qt Licensing Policies

[Kevin K. <kr...@kd...>]

On Monday, 2013-08-12, Ryan Bramantya wrote:

> > This approach has some drawbacks as well.
> > When you choose LGPL, then you cannot use GPL'd code from other project,
> > either.
> > For example, if we find a good piece of code in KDE that suit our
> > need, we cannot use it if it's GPL'd. It's the price we need to pay.
> 
> I think you don't need to worry, because as Kevin has said: "Anything a
> developer might use -> LGPL, anything only an end user would use -> GPL".
> It means KDELibs, KParts (library for building KDE applications such as
> Okular, Kopete, etc), and other good library things from KDE wasn't GPL.
> The only thing that may be worth for building a desktop environment, but
> under GPL is KWin.

Sure, but in such a case it might be more viable to use KWin as a whole 
instead of taking some pieces of it and then maintaining them yourself.
It might also not be easy to extract that code, application code tends to 
depend on other parts of the application, e.g. singletons.
It will likely also come without API docs.

> After all, I just want to convey that LXDE isn't GNU/Linux centric, LXDE is
> for everyone in mind (BSD community, Apache community, common user, etc)
> even though it may be developed in Linux environment.

Sure, but that isn't a licensing problem. KDE software, for example, is being 
used on operating system ranging from extremely persmissive to fully 
proprietary.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring