From: Markus H. <ma...@ti...> - 2009-10-26 16:54:35
|
I would understand it in this way: The resulting Obj/C source (the *.m and *.h files) is always under GPL. The original java code can remain under any license you want, as long as you don't link to xmlvm files in there (import org.xmlvm.iphone.*). So converting an Android app, that does not use any xmlvm code in the java source, will not have to be under GPL. Only the resulting *.m and *.h files will. But writing directly to the xmlvm compatibility API (import org.xmlvm.iphone.*) will force you to make your java code GPL, too. Is this understanding correct? If not could you explain why not? :) And maybe you should define what a major revision update is. Is 1.0- >1.1 major or 1.0->2.0? Markus Am 26.10.2009 um 17:14 schrieb Arno Puder: > > Guys, > > a while ago we had a longer discussion regarding commercial usage of > XMLVM. We (the XMLVM core team) explained our dual licensing strategy, > but we have not yet explained what constitutes a contribution for > which > we will grant the non-transferrable linking exception. > > We had an internal discussion to clarify this point and we would > like to > solicit feedback from you. > > Arno > > --- > > XMLVM is released under the GPL license. If you use XMLVM to translate > your application, the resulting source code will also be under the GPL > license. If you would like to use XMLVM for a commercial product and > do > not want to release the source code of your application (as required > by > the GPL), we offer you a non-transferrable linking exception in return > for a contribution to the XMLVM project. The linking exception will > enable you to publish a commercial application build with XMLVM > without > having to release your own source code. > > There are different ways to make a contribution to the XMLVM project > for > which we will grant you the non-transferrable linking exception. One > option is to submit a substantial patch to increase the quality of > XMLVM. Please ask us if you want to clarify whether your proposed > patch > qualifies as substantial. > > Another option to make a contribution to XMLVM is by making a > donation. > We will grant the non-transferrable linking exception of the current > version of XMLVM for US $300 per developer. The $300 donation will > give > the developer the right to use the current version of XMLVM without > having to release the source code of his/her applications. This > donation > covers minor revisions (bug fixes). Major revision updates of XMLVM > can > be obtained by an additional US $100 per developer. > > If XMLVM is lacking certain features that you need for your > application, > we also offer to implement those missing features on a contracting > basis. Please contact us for details. > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |