Community mailing list archives

Re: Enterprise: Is it allowed to use AGPL community modules?

Blanco Martin y Asociados , Daniel Blanco
- 10/05/2015 19:43:53
Nice Quote "a new area of dog eat dog"..unfortunatedly

Quedo atento a sus comentarios. Saludos:

Ing. Daniel Blanco
Blanco Martín & Asociados
Móvil: +56 9 73880409 / +54 9 351 228-0893
Skype: hdanielb
Twitter: hdanielb

Blanco Martín EIRL
Apoquindo 6410 Of 212
+56 2 2840 0990 / +56 2 2979 0208
Las Condes - Región Metropolitana

Nicasio 6970. Córdoba
+54 351 5694621 / +54 351 5691933
Argüello - Córdoba

2015-10-05 15:08 GMT-03:00 Raphaël Valyi <>:

my biggest point for not allowing AGPL and proprietary module to cohabit is the legal risk because of this feature that is central to the Odoo framework:

That is if for instance I create a proprietary e-commerce module where a sale order can be placed. Then imagine there is a button that create an invoice from the order. Despite that proprietary module may not explicitly depend say on localization X that is AGPL, technically speaking in its code there will be something like sale_order.create(...).
Then this is the Odoo framework itself that will call any method overriding the original create method even if the proprietary e-commerce module doesn't depend on them. That is, in country X the proprietary e-commerce module will take advantage of localization X (say tax computation, correctness of the fiscal documents...) without technically depending on localization X. This also creating common structures n the same memory space inside the same operating system process, what is called by the *GPL "static linking".

If that would have to go to court, this is I believe the point where people should insist on.

Now, about the mix in general. Before with the AGPL, the community and even Odoo SA could discredit and kind of commercially blacklist any SaaS offering featuring non released modules and keep that pirate offer very marginal.

Now the problem with the new licensing sh*t is that one will hardly prove how exactly AGPL and proprietary modules interact exactly on these opportunist SaaS platforms to happen. So typically, in some countries with strong IP law enforcement, big players will eventually refrain themselves from taking that legal risk. Mostly the victims will be the official Odoo partners who will expose them to being banned if they do so without even things to have to go a court while their unofficial competition will certainly do it. Nice time to be an Odoo partner as some mentioned...
On the contrary, in many other countries, fearless outsiders will certainly derivate AGPL modules into proprietary modules. And they will also certainly make their way to approach the Enterprise modules (via fake customers or temporary partnerships etc...) to also offer clones of the Enterprise modules too... And even companies larger than Odoo SA themselves may play that game... So IMHO not even Odoo SA will benefit from this license change...

As I always told we all just lost a good opportunity to have a sane eco-system. This is a whole new area of dog eat dog beginning now...

On Mon, Oct 5, 2015 at 12:58 PM, Anders Wallenquist <> wrote:
I think there are many authors of AGPL-modules that don't want their 
modules do be mixed with non GPL-modules. That is the purpose with AGPL.


Anders Wallenquist

Den 2015-10-05 kl. 17:38, skrev Dominique Chabord:
> hello,
> It is a very sensible subject documented in several places.
> Let me summarize my understanding in two rules:
> - if the AGPL module is copy-righted by OCA, then OCA grants you the
> right to combine with Enterprise here
> . There is no mention in the code
> itself about this loose interpretation of the license, so if you
> consider this FAQ can be updated overtime, may be you can ask OCA for
> a document you can archive.
> - if the AGPL module is not copy-righted by OCA, refrain mixing it
> with any non GPL (AGPL, GPL, LGPL or compatible) module if you don't
> get a written authorization from all copyright holders. Else you would
> expose to conflicts.
> Some hosters (I'm one of them) adopt a restrictive interpretation of
> AGPL and forbid any combination of AGPL module with other modules
> under uncompatible licence as a potentially illegal usage on the
> servers they are responsible for.
> 2015-10-05 16:59 GMT+02:00 Ermin Trevisan <>:
> > Hi all
> >
> > Just to be truly sure: Is it legally possible to install AGPL licensed
> > community modules on an enterprise installation? If yes, under what
> > circumstances?
> >
> > Best, trevi
> > --
> > twanda AG
> > Ermin Trevisan
> > Artherstrasse 19
> > CH-6318 Walchwil
> > T    +41 41 758 1515
> > M +41 79 208 7373 > > E > > > > > > > > _______________________________________________ > > Mailing-List: > > Post to: > > Unsubscribe: > > _______________________________________________ > Mailing-List: > Post to: > Unsubscribe: >

Post to:


Post to: