@turkinigor,
> But my customer don't wanna share his customizations and integration source > code, and it is proper decision. Make no mistake. linking to GPL code, allows to you develop once a module that you will never be publish, for yourself or only one customer (you should give him the source however and the customer should be free to publish it as GPL). What is not allowed by GPL, is, just like some very few bastards companies seems to do unfortunately, is that you develop a module linking to OpenERP (having a dependency upon objects defined in GPL code of OpenERP) and then resale it to several folks/customers, without publishing the source publicly under the GPL. Now, there are also workarounds and you can play with limits. You can for instance control OpenERP remotely using webservices with frameworks such as OOOR http://code.google.com/p/ooor/ (or some M$ designer plugins) and not redistribute the code because it doesn't "link" to OpenERP objects in memory buy simply interoperate with it with text messages (webservices). Still, working with open source without being really part of it, is just a plain stupid short term vision IMHO. Hope this helps ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=44846#44846 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
