Hi Benjamin,
Thanks for join in this discussion.
just my two cents: In the same way it is possible to license a program
> as GPL2 and GPL3, it is also possible to license a program under LGPL
> and GPL. Then, if one wants to use a component, that is GPL only, one
> can simply drop the LGPL license from that point. So, if you want to
> use a copyleft license but have no prejudice about how strong the
> copyleft should be, you might triple license GPL2+/LGPL2+/MPL to cover
> the most widespread incompatible copyleft licenses and leave as many
> possibilities open as possible. (Incidentally, that is what
> LibreOffice does.)
>
I think there is no need to use tri-license. Based on LGPL licensing
policy, it said that LGPL can be converted to GPL (but not vice versa).
Therefore, by chosing LGPL as license, if someone want to create GPL
software, the just converting it to GPL and if some one want to create BSD
or proprietary software and avoid LGPL, the just dynamically linking their
software to LGPL component which wouldn't affect their BSD or proprietary
license. This is what I see as the advantage of LGPL from any other license.
--
Best regards,
Ryan Bram
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxde-list
