On 13-08-12 01:24 PM, Ryan Bramantya wrote: > > 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. >
In fact, one of the bloggers on Planet Mozilla just (as in within the last hour) announced that they'd finished retiring the LGPL/GPL/MPL tri-license in favor of the MPL2. http://blog.gerv.net/2013/08/mpl-2-upgrade-process-complete/ (The MPL2 was specifically written to support that kind of conversion chain so the tri-license wouldn't be necessary) https://en.wikipedia.org/wiki/Mozilla_Public_License#Compatibility_with_other_licenses ------------------------------------------------------------------------------ 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
