Yes, the idea is to add Apache as a third possible license. Will that be a problem ?
The only thing I can see, is that it would force other developper, on that contrib, to also accept their correction to be under that triple licences. It should not be a problem. I'm open for MIT but like Apache products. We're using a lot of them. Current qooxdoo RPC-Java contrib use Apache beanutils framework. On Jan 20, 2010, at 17:46 , Petr Kobalíček wrote: > Hi Fabian, > > sorry I didn't understand topic correctly, I talked only about adding > third license (the Apache one) as a possible license for the java-rpc. > I talked about this with original java-rpc author and he permitted it > (so I though that it's without problems). I think that adding apache > license as third one is not restriction, it just make java code > license compatible with many others. > > -- > Best regards > - Petr Kobalicek <http://kobalicek.com> > > On Wed, Jan 20, 2010 at 4:27 PM, Fabian Jakobs <[email protected]> wrote: >> Petr Kobalíček schrieb: >>> 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. >>> >> Dual licensing and licens compatibility are completely different topics. >> If a software is released with a dual license the use of the software >> can choose either license. >> >> License compatibility becomes important if you want to incorporate code >> with a different license into a project. For example if we want to >> include code with an Apache license into qooxdoo, which is LGPL/EPL, the >> apache license has to grant the user at least the same rights as LGPL >> and EPL. Otherwise qooxdoo as a whole would no longer be under the >> LGPL/EPL. What Andreas is saying is that the Apache license apparently >> has a clause, which makes it impossible to distribute it as LGPL and EPL. >> >> One solution would be to use the Apache license as an additional third >> license to grant users more rights. The other one would be to use the >> BSD or MIT license. >> >>> 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. >>> >> No this will not be a problem as long as all authors agree to the >> license change. >> >>> 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) >> Exactly. >> >> Best Fabian >> >> -- >> Fabian Jakobs >> JavaScript Framework Developer >> >> 1&1 Internet AG - Web Technologies >> Ernst-Frey-Straße 9 · DE-76135 Karlsruhe >> Telefon: +49 721 91374-6784 >> [email protected] >> >> Amtsgericht Montabaur / HRB 6484 >> Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas >> Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver >> Mauss, Jan Oetjen >> Aufsichtsratsvorsitzender: Michael Scheeren >> >> >> ------------------------------------------------------------------------------ >> 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 ------------------------------------------------------------------------------ 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
