From: Laurent Le B. <Lau...@on...> - 2004-10-20 08:20:50
|
Hello, It seems that the version 0.9.8 of OpenObex was LGPL and now the current version 1.0.1 is completely GPL. If I use version 0.9.8, can I still assume it is LGPL or since a more recent version has been released under GPL, the previous versions automatically become GPL ? I would appreciate any link on this to be sure that we carefully respect the different licenses. Moreover, regarding GPL associated with OpenObex, does anybody know how we could use OpenObex in a commercial product which cannot be open source ? The idea is to add features to OpenObex such as TAPI in OpenObex. These developments would be of course Open Source but then we need to use this library in a commercial product. Any information on how we could do this properly ? Best regards, Laurent ONDIM Si=E8ge social 14, rue Soleillet 75020 PARIS T=E9l : 33 (0) 1 40 33 88 00 Fax : 33 (0) 1 40 33 65 54 Gsm : 33 (0) 6 08 41 48 20 Email : lau...@on...=20 |
From: Marcel H. <ma...@ho...> - 2004-10-20 08:47:02
|
Hi Laurent, > It seems that the version 0.9.8 of OpenObex was LGPL and now the current > version 1.0.1 is completely GPL. > If I use version 0.9.8, can I still assume it is LGPL or since a more > recent version has been released under GPL, the previous versions > automatically become GPL ? > > I would appreciate any link on this to be sure that we carefully respect > the different licenses. the 1.0.1 version is still LGPL as long as you compile it without IrDA and Bluetooth support. I messed that up, sorry for the confusion. > Moreover, regarding GPL associated with OpenObex, does anybody know how > we could use OpenObex in a commercial product which cannot be open > source ? With the LGPL version of the library. See statement above. > The idea is to add features to OpenObex such as TAPI in OpenObex. These > developments would be of course Open Source but then we need to use this > library in a commercial product. Any information on how we could do this > properly ? No problem. Go ahead and send your patch to the mailing list. Regards Marcel |
From: Laurent Le B. <Lau...@on...> - 2004-10-20 10:59:54
|
Thank you Marcel for your answer. In fact, we would need the IrDA support for our commercial product so is there a way to use OpenObex with IrDA in a commercial product that can not be open source ? Regards, Laurent ONDIM Si=E8ge social 14, rue Soleillet 75020 PARIS T=E9l : 33 (0) 1 40 33 88 00 Fax : 33 (0) 1 40 33 65 54 Gsm : 33 (0) 6 08 41 48 20 Email : lau...@on...=20 -----Message d'origine----- De : ope...@li... [mailto:ope...@li...] De la part de Marcel Holtmann Envoy=E9 : mercredi 20 octobre 2004 10:47 =C0 : OpenOBEX Mailing List Objet : Re: [openobex-users] LPGL then GPL on OpenObex - Commercialproduct with OpenObex Hi Laurent, > It seems that the version 0.9.8 of OpenObex was LGPL and now the=20 > current version 1.0.1 is completely GPL. If I use version 0.9.8, can I > still assume it is LGPL or since a more recent version has been=20 > released under GPL, the previous versions automatically become GPL ? >=20 > I would appreciate any link on this to be sure that we carefully=20 > respect the different licenses. the 1.0.1 version is still LGPL as long as you compile it without IrDA and Bluetooth support. I messed that up, sorry for the confusion. > Moreover, regarding GPL associated with OpenObex, does anybody know=20 > how we could use OpenObex in a commercial product which cannot be open > source ? With the LGPL version of the library. See statement above. > The idea is to add features to OpenObex such as TAPI in OpenObex.=20 > These developments would be of course Open Source but then we need to=20 > use this library in a commercial product. Any information on how we=20 > could do this properly ? No problem. Go ahead and send your patch to the mailing list. Regards Marcel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Openobex-users mailing list Ope...@li... http://lists.sourceforge.net/lists/listinfo/openobex-users |
From: Martyn <ma...@jo...> - 2004-10-20 12:59:15
|
On Wednesday 20 October 2004 11:59 am, Laurent Le Bourhis wrote: > Thank you Marcel for your answer. > > In fact, we would need the IrDA support for our commercial product so is > there a way to use OpenObex with IrDA in a commercial product that can > not be open source ? Easy, rewrite the IrDA component, releasing it as LGPL, then you can use it too. BUT - you must do it clean, not by looking at the existing source. The GPL is designed to protect people from commercial products making money on the backs of those people who give their time and efforts freely. IMHO You should respect that and release your product GPL too - the GPL does not prevent you charging for distribution, just means you must make the source available too. > Regards, > Laurent -- Martyn Ranyard |
From: Laurent Le B. <Lau...@on...> - 2004-10-20 13:57:47
|
Hello Martyn, I completly agree with the principles of GPL, that is why I've asked this question honestly. My current problem is that our targeted application have some critical code that we cannot disclose. In fact, the final application is free but proprietary ! > Easy, rewrite the IrDA component, releasing it as LGPL, then you can use it=20 > too. BUT - you must do it clean, not by looking at the existing source. Looking at irobex.h and irobex.c, the headers says that the code is under LGPL. So what is the status ? I am quite lost in the different headers of the library... Moreover, if we have no other solution than rewriting the IrDA component, is there any test application we could use to validate our development ? Regards, Laurent ONDIM Si=E8ge social 14, rue Soleillet 75020 PARIS T=E9l : 33 (0) 1 40 33 88 00 Fax : 33 (0) 1 40 33 65 54 Gsm : 33 (0) 6 08 41 48 20 Email : lau...@on...=20 |
From: Martyn <ran...@li...> - 2004-10-20 14:50:16
|
On Wednesday 20 October 2004 2:57 pm, Laurent Le Bourhis wrote: > I completly agree with the principles of GPL, that is why I've asked > this question honestly. My current problem is that our targeted > application have some critical code that we cannot disclose. In fact, > the final application is free but proprietary ! One thing you could do is make a proprietry library/plug in that obexftp can link to - this is not prohibited but frowned upon by the opensource community - see the removal of the Philips Webcam driver from the kernel for some insight. You may find a way forward which means you could send in some code to openobex that exposes hooks that can be used by your proprietry code - then it's just up to the maintainers to decide if this is a good thing, and if they don't you'd have to fork. Not nice but possible. > Looking at irobex.h and irobex.c, the headers says that the code is > under LGPL. So what is the status ? > I am quite lost in the different headers of the library... I'm not a hacker on this project, maybe someone else could advise on this. It may be that these interface to a GPL library. Maybe an older version could be used and linked in with the current version's main code. > Moreover, if we have no other solution than rewriting the IrDA > component, is there any test application we could use to validate our > development ? I would have thought obexftp, but again, I'm not a hacker on this project, only an ex-user (my phone was stolen). -- Martyn |
From: Marcel H. <ma...@ho...> - 2004-10-20 14:51:42
|
Hi Laurent, > I completly agree with the principles of GPL, that is why I've asked > this question honestly. My current problem is that our targeted > application have some critical code that we cannot disclose. In fact, > the final application is free but proprietary ! > > > Easy, rewrite the IrDA component, releasing it as LGPL, then you can > use it > > too. BUT - you must do it clean, not by looking at the existing > source. > > Looking at irobex.h and irobex.c, the headers says that the code is > under LGPL. So what is the status ? > I am quite lost in the different headers of the library... > > Moreover, if we have no other solution than rewriting the IrDA > component, is there any test application we could use to validate our > development ? look at the file irda.h and you may wanna simply ask Dag Brattli for a LGPL version of it. If he agrees, put me on CC and I change that file for the next OpenOBEX release. Regards Marcel |
From: Raj M. <ra...@li...> - 2004-10-20 13:34:07
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Laurent" == Laurent Le Bourhis <Lau...@on...> writes: Laurent> Thank you Marcel for your answer. In fact, we would need Laurent> the IrDA support for our commercial product so is there a Laurent> way to use OpenObex with IrDA in a commercial product Laurent> that can not be open source ? Do you mean ``proprietary'' when you say ``commercial''? All GPL/LGPL software is commercial, and I'll happily legally sell you a copy of Obexftp for $500 if it helps drive home the point! :) Regards, - -- Raju - -- Raj Mathur ra...@ka... http://kandalaya.org/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F It is the mind that moves -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQFBdmjryWjQ78xo0X8RAvN6AJ9xT2hQUm8QiFZzWunG5lJcYAVdjwCfeU9u lj47AxE3pnlSriadfO+yYc8= =ZImy -----END PGP SIGNATURE----- |
From: Laurent Le B. <Lau...@on...> - 2004-10-20 13:49:20
|
Thank you Raju for your offer ! :) I indeed meant proprietary. ONDIM Si=E8ge social 14, rue Soleillet 75020 PARIS T=E9l : 33 (0) 1 40 33 88 00 Fax : 33 (0) 1 40 33 65 54 Gsm : 33 (0) 6 08 41 48 20 Email : lau...@on...=20 -----Message d'origine----- De : ope...@li... [mailto:ope...@li...] De la part de Raj Mathur Envoy=E9 : mercredi 20 octobre 2004 15:33 =C0 : ope...@li... Objet : Re: RE : [openobex-users] LPGL then GPL on OpenObex - Commercialproduct with OpenObex -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Laurent" =3D=3D Laurent Le Bourhis <Lau...@on...>=20 >>>>> writes: Laurent> Thank you Marcel for your answer. In fact, we would need Laurent> the IrDA support for our commercial product so is there a Laurent> way to use OpenObex with IrDA in a commercial product Laurent> that can not be open source ? Do you mean ``proprietary'' when you say ``commercial''? All GPL/LGPL software is commercial, and I'll happily legally sell you a copy of Obexftp for $500 if it helps drive home the point! :) Regards, - -- Raju - --=20 Raj Mathur ra...@ka... http://kandalaya.org/ GPG: 78D4 FC67 367F 40E2 0DD5 0FEF C968 D0EF CC68 D17F It is the mind that moves -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/> iD8DBQFBdmjryWjQ78xo0X8RAvN6AJ9xT2hQUm8QiFZzWunG5lJcYAVdjwCfeU9u lj47AxE3pnlSriadfO+yYc8=3D =3DZImy -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Openobex-users mailing list Ope...@li... http://lists.sourceforge.net/lists/listinfo/openobex-users |
From: Marcel H. <ma...@ho...> - 2004-10-20 18:30:15
|
Hi Raju, > Do you mean ``proprietary'' when you say ``commercial''? All GPL/LGPL > software is commercial, and I'll happily legally sell you a copy of > Obexftp for $500 if it helps drive home the point! :) put they still must give me the source if I asked and linking with a GPL library makes there software also GPL. This is the problem with IrDA and Bluetooth support of OpenOBEX. The irda.h header file is GPL, because it is derived from the IrDA part of the Linux kernel and the Bluetooth library is also GPL. Regards Marcel |