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
