I agree with Humberto, If you want use license you should not go for OpenERP but rather to SAP, Dynamics or another proprietary ERP.
2013/2/11 Humberto Arocha <humbertoaro...@gmail.com> > The thing here is Why are you that worry about closing on something that > has prove to be yet more a comercial success with its openness approach > > Regards > On Feb 10, 2013 4:15 PM, "Jerzy Orłowski" <jerzy.orlow...@lacan.com.pl> > wrote: > >> I think you miss one point. Getting the source code is not enough to >> use it. You still need the license from the author that allows you to >> republish the code, use it in your own own programs, etc. >> >> Is it possible to find a solution, where openerp and the core modules of >> openerp is open source, but OpenERP allows to build other modules with >> commercial licences? I'm not an expert in licenses but it all goes with the >> question about the nature of AGPL and licences compatibility. >> >> I am quite sure that it is possible to create a comercial software that >> would communicate with OpenERP via xml-rpc. >> But the question is, is it possible to create a closed-license OpenERP >> module. >> >> Assume that somebody writes an OpenERP module without copying a line of >> code from OpenERP AGPL licenced modules. >> I am quite sure that at this point you can licence it however you want >> and distribte it in any way you want. >> >> There are several important questions that have to be answered. >> 1. Can you distribute the module together with other OpenERP AGPL >> licenced modules? >> 2. Can anyone who bought this module import it to OpenERP (Assuming that >> he or she uses it internally in his/hers company)? >> 3. If a company A who bought this module shows the system to company B, >> can company B ask company A to show him/her the source code of this module >> because of OpenERP AGPL license? >> 4. If a company A who bought this module shows the system to company B >> and company C gets info that such module exists, can company C ask for the >> source code ot the module? >> 5. If answers for the questions 3 or 4 is "Yes", can the license in the >> module forbid the company B or C to use the code, publish, sell, change, >> incorporate any programs? >> 6. If answer for the question 5 is "Yes", can you distribute a "dirty" >> version of the code, for example with names of the variables chanded, with >> no comments, with all xml, yaml, rml, css files taken out. >> >> I think that if we answer these five questions we will get the answer, >> whether it is possible to create any "sellable" OpenERP modules. >> >> Does anyone have any answers to any of the these question. >> >> W dniu 09.02.2013 15:52, Christophe Hanon pisze: >> >> It means for me what it means for many licences authors : software is >> distributed with the source code. As explained for example in GPL, AGP >> licences.**** >> >> ** ** >> >> Kind regards**** >> >> ** ** >> >> Christophe**** >> >> ** ** >> >> ** ** >> >> ** ** >> >> ** ** >> >> *From:* Alberto BARRIONUEVO [mailto:abar...@opentia.com<abar...@opentia.com>] >> >> *Sent:* 07 February 2013 10:49 >> *To:* Christophe Hanon >> *Cc:* Arun Venkat; Luc De Meyer; 'Bertrand Hanot'; 'Nabil Majoul'; >> 'Serpent Consulting Services'; openerp-community@lists.launchpad.net; >> partn...@openerp.com >> *Subject:* Re: OpenERP: [Openerp-community] Partners Collaboration Model* >> *** >> >> ** ** >> >> Hi Christophe, >> >> El 06/02/13 12:17, Christophe Hanon escribió: **** >> >> So I think more quality modules will be published the day publishers can >> get a minimal fee for their code.**** >> >> This is not incompatible with open-source - see the joomla extensions web >> site. Free and commercial are equally published but all in open-source. >> **** >> >> What means "open-source" for you? >> >> **** >> >> -- **** >> >> Alberto Barrionuevo, Director**** >> >> Grupo OPENTIA**** >> >> OpenERP Partners**** >> >> T (+34) 918 38 38 58**** >> >> F (+34) 944 34 00 77**** >> >> ** ** >> >> OPENTIA**** >> >> Ingeniería Informática en Abierto**** >> >> www.opentia.com**** >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openerp-community >> Post to : openerp-community@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openerp-community >> More help : https://help.launchpad.net/ListHelp >> >> >> >> -- >> >> Pozdrawiam serdecznie, >> >> Jerzy Orłowski >> >> Członek Zarządu ds. technologii >> Al. Stanów Zjednoczonych 53 >> 04-028 Warszawa >> tel. +48 (22) 266 01 02 >> tel. +48 (22) 292 16 16 >> kom. 668 151 245www.lacan.com.pl >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openerp-community >> Post to : openerp-community@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openerp-community >> More help : https://help.launchpad.net/ListHelp >> >> > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : openerp-community@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : openerp-community@lists.launchpad.net Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
