Members mailing list archives

Re: OCA's statement on the announced change of license of Odoo

Avanzosc, S.L., Ana Juaristi
- 07/02/2015 15:20:33
I understand almost nothing about licenses but we decided to publish everything AGPL, just because we want people using our modules or extending the functionality we develop was not allowed to hide their work. 

I see right that Odoo as editor decides the kind of licence that is good for their bussiness and I like the decision of selecting LGPL because I can use the base modules with our own and other community AGPL modules. 

I can also say that if Odoo would like to use some of our modules or include them into core I would allow changing their licence to LGPL. Here... I would ask OCA about this question because I think that at the end the OCA objective should be not only mantaining community modules but to offer the best ones to be included on Odoo Core future versions.
But... if another enterprise/partner wants to modify our code they would have to publish in AGPL so it's mandatory for them to revert their investment to community and they wouldn't be allowed to hide their improvements.

That's the way I think. I don't mind if someone makes money with our work but if they are able to improve it, they have got to revert it to community so... to us. Maybe not with direct money but just with R&D and work. For me... it's just the same.

Thank you:


2015-02-07 14:51 GMT+01:00 Christophe Hanon <>:
Dear community,

may be I am the only one, but I don't like AGPL because it put duties on the organisation running the software. You buy a 2$ mug from a shop and then you can ask the complete source code a the webshop, same for any employee working a day in a company. These are things customer don't want and IMHO most integrators don't explain it to their customers because if they do so, the customer run away...

This licence obligations without commercial action about the software itself makes also Odoo in open-source licence (I mean without enterprise private modules incompatible with use of any software patent / copyright which is again a problem. 

The repeated argument is about somebody making money with the software without contribution to the communitty. I thing it is more a human-psychology issue than anything else and symptomatic a non assumed open-source model. May be somebody will make a fortune writting a book with LibreOffice... So what ? I make money using Python and Postgres... So what ?

I respect a lot those who contribute their code and work, one way or another. On the other side, a lot of these contributions on the Odoo eco systems are unfinished, unsupported work. I think commercial offering will increase availability of more finished solutions and those who have such solutions will finally be enabled to advertise them instead of hidding themselves. In a way this will make the 'odoo market' more transparent and more efficient. 

Please note that having the framework LGPL (or similar business friendly licence) is the only way to get it seriously face to face with other frameworks. 

For that reason, I fully support the licence change. Odoo keeps the software open-source and accepts that others are also making business with it. This is true open-source spirit. I think it is the best move concerning the business model since I follow the product and it does not exclude cooperation like the OCA projects.

I did not like the idea of a restricted distribution of the latest version because it would slow down adoption of the product. However I can live with commercial products by Odoo or others. For example mobile apps, connectors, wysiwig report engine etc I am sure this will provide a lot of nice solutions that cannot be easily founded by a project to a single customer.

Finally, each contributor may have his opinion about how he wants to share his work. But I think AGPL modules on top a LGPL framework, mixed with proprietary modules can only make good to layers wallets. For that reason I think the only right solution for open-source contributors willing to ensure the open-source aspect without impeding the usage of its contributions (thus assuming the open-source model completely) is to use the GPL licence.

Have a great week-end !


Christophe Hanon 

On Fri, Feb 6, 2015 at 7:12 PM, StéphaneWirtel <> wrote:
On 6 Feb 2015, at 17:53, Alberto Barrionuevo wrote:

> On 06/02/15 16:27, StéphaneWirtel wrote:
>> On 6 Feb 2015, at 15:03, Luc Maurer wrote:
>>> Sorry, Stéphane but why "Bad for the community" ?
>>> As LGPLv3 is compatible with AGPL the community has the choice ! if
>>> you want to protect your dev than you choose AGPL and if you are 
>>> more
>>> "open" then you choose LGPL => where is the problem ?
>>> A+
>>> Luc Maurer
>> If I am a company and I don't want to share my code, I won't use the
>> AGPL.
>> Is it right?
> But if you use modules/code that are AGPL and you develop on top of
> them, you are forced to license that code under AGPL.

If your module is just a leaf in your dependencies graph, you can 
rewrite it with an other license.

And keep the code closed.

And about your question, I don't know :/ Hope yes.
Stéphane Wirtel - - @matrixise

Post to:


Christophe Hanon - ADINS

Tel +32 (0) 10 81 47 32

Fax + 32 (0) 10 81 91 84

Mobile +32 (0) 475 63 79 65 &


ADINS est signataire -numéro d'enregistrement 435 - de la charte de déontologie

« eTic » consultable à  l'adresse

Post to:

CEO Avanzosc, S.L : Office phone / Tfono oficina: (+34) 943 02 69 02
Ana Juaristi Olalde : Personal phone: 677 93 42 59. User/usuario skype: Avanzosc

El contenido de esta comunicación y de toda su documentación anexa es confidencial y se dirige exclusivamente a su destinatario. El uso no autorizado de esta información está prohibido por la legislación vigente. Si usted no es el destinatario le rogamos nos lo indique, no comunique su contenido a terceros y proceda a su destrucción. Disculpe las molestias que le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse para ejercer sus derechos de acceso, rectificación, cancelación y oposición en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -

Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 -

This message and all documents attached to it are confidential and intended only for the person or entity to which it is addressed. Any use of this information by unauthorised persons is prohibited under current legislation. If you received this message by error, please advise us, destroy it and refrain from communicating its contents to third parties. We apologise for any inconvenience receiving this email improperly may cause to you. Your personal data are included in a file owned by Avanzosc, S.L. If you want to exercise your rights of access, correction, erasure and objection you can contact the Controller at Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), T: 943 02 69 02 –