I don't understand, for example jquery is dual licensed as MIT and GPL, is this in conflict (because these licenses are SO different)? If you release some sw under three licenses then there is no conflict, because users have choice.
I'm only pointing out that if I have choice then I choose the sw library under BSD/MIT/Apache over LGPL, and I'm not alone here. You are showing here license conflicts, but you forgot to say that using LGPLv2 library in GPLv3 product is also license conflict, but I hope that discussion is not about this. Quetion was, will be in conflict to add third license (Apache) to the java-rpc package? I think that there is no conflict and original author of java-rpc permitted it. And if you have problem with Apache license then we can simply choose the MIT one (it's really simple, you can print in on single page). -- Best regards - Petr Kobalicek <http://kobalicek.com> On Wed, Jan 20, 2010 at 2:30 PM, Andreas Ecker <[email protected]> wrote: > Hi JBB! > >> We are in the process of delivering a qooxdoo contrib so the code must >> be dual licensed under LGPL and EPL. >> http://qooxdoo.org/license >> >> >> Is it possible to also give the code under Apache license ? > > Wouldn't be the LGPL/EPL dual license just be fine for your contrib as > well? Unless your code requires to be put under Apache for some specific > reasons, I'd suggest to go with LGPL/EPL. This would nicely fit into the > qooxdoo ecosystem. > >> Will it "conflict" ? > > If you only put it under Apache: yes, this would conflict. Apache > License and LGPL (below v3) are non-compatible licenses. > > So I would not suggest to try to introduce the Apache license here. If > there are some specific reasons for an add'tl Apache licensing, you > might think of a tri-license LGPL / EPL / Apache. > >> How to do that ? Is it just a matter of writing it in the contrib >> license file ? > > You should include an appropriate license file with your contrib. > Additionally you should have correct file headers (copyright, license, > authors, ...) for all relevant source files. See the framework or other > contribs for reference. > >> Are one of you aware of why or why not Apache license are not more >> widely used in the qooxdoo community ? > > Each ecosystem has its preferred set of licenses. For qooxdoo, its LGPL > and EPL, also due to the inherent LGPL/Apache incompatibility. > > HTH, > > Andreas > > -- > Andreas Ecker > Project Lead > http://qooxdoo.org > > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
