Community mailing list archives

Re: Odoo v9 Community and Enterprise editions

Camptocamp SA, Joël Grand-Guillaume
- 05/13/2015 07:58:03

I've asked my colleague at Camptocamp about Puppet community. Puppet was first GPL and become Apache based (so similar to MIT). All contribs are released under this license on a forge. In the ecosystem, you find:

 * Official Puppet module supported by the company
 * Approved module by PuppetLabs from the community
 * Community module

The Approved  module by PuppetLabs are the best module in a given area. They test for example 10 modules for managing OpenSSL and they elect the best one. So everyone knows that this is the best and that everyone should contribute to it. This give a lot of good marketing for the author of an approved module. This way, you avoid having hundreds of same modules, everyone share effort on a single one.

Then as it is Apache based, PuppetLabs may take some of the community work to make their enterprise package and sell it. Puppet Enterprise is then sold as a package of Official & may be Approved module + some Glue around them. PuppetLabs take all the money in that case, not the author.

The thing is we can see various differences with Odoo world:

 * Puppet is low level software, not for end user. For Odoo it is the contrary.

 * Puppet is not offering a Saas, but a complied package charged to the customer based on the numbers of server it'll manage. They make money on the arrangement / the glue of the various elected modules.

 * They empower their community by electing the best modules (once you're module is approved, you get hundreds of contribs !)

 * The community is happy to share the work because PuppetLabs give back to the community in the form of reputation, visibility and a great R&D spent on improving the tools.

 * Nobody sells module in this ecosystem

Finally, it also exists a kind of OCA in the Puppet world called Puppet community :

As a conclusion, I think the world of PuppetLabs is really different from Odoo as the 2 software really server different market and purpose. It's hard to imagine how to transpose the Puppet way in Odoo world, but we can notice:

 - about how they empower their community and play a role in the recognition of the good modules.
 - in this infrastructure world, you don't really fear the Customer lock-in, in an ERP one yes (main reason why we want to keep AGPL)
 - in the Puppet world, nobody sell modules
 - the value puppet is selling is their easy-to-use package, selected and put together in a consistent manner that spare lot's of time to final user and sysadmin

There is no real point that get out of this little story to help us on the topic, but I found it interesting to share it anyway.



On Wed, May 13, 2015 at 1:22 PM, Gunnar Wagner <> wrote:
+1 to Anders (again)

I think it's not the right approach to try to find any workable solution to deal with this mess. Why would anybody who did not create this situation (Community, OCA) try to comply to the one that puts the fundamentals at stake (S.A.)
Did nobody ever hear the term "identification with the aggressor" before? That is in my eyes what trying to find whatsoever friendly compromise in order to satisfy the needs of S.A. in this matter basically comes down to.
First and foremost the Community should be clear that an attack is being conducted. And that does not require a 'friendly' response I think. The one being attacked should defend itself (or the idea that is to be protected).

On 5/13/2015 6:52 PM, Anders Wallenquist wrote:
<blockquote cite="" type="cite">
Den 2015-05-12 18:39, Alan Bell skrev:
> On 12/05/15 15:58, Christophe Hanon wrote:
> > I think a licence checker based on dependencies would be great...
> >
> > Regards,
> >
> > Christophe
> >
> my favoured solution too, if we can all agree that in the context of
> Odoo, the best way to interpret the license in terms of the meaning of
> derivative works is through dependencies then it could be set so that
> pretty much anything can depend on LGPL modules, GPL or AGPL can depend
> on GPL modules and only AGPL modules can depend on AGPL modules. This
> dependency rule can be implemented in the code and we could have a
> facility to automatically provide the source
> of the AGPL bits.
> Can anyone see a downside to this?

Well to implement a licence hell are fundamental wrong. If Odoo SA wants 
that Odoo still be a star in free software area the cost of a licence 
hell will kill the community and the product in the long run. To "sell" 
Odoo to new customers you have to look at each module and calculate if 
they will fit together in a licence matter. To create a qoutation 
sometimes a couple of hundred modules have to work together. It's not 
enough that you know its right functionality and you know by experience 
it right for the case, you have to know if any of the other modules 
disqualifies the use of this module in this case. Even if you have 
automatic checks at installation time it will not work. You'll have to 
build the installation before you can create a quotation.

You have to educate your customer what modules they can use and what 
they cannot and why overtime when they want to grow theit business with 

No if Odoo shall remain as a free software product as we know it has to 
have compatible licences in all modules payed or not.

Odoo SA have lost the perspective in this new strategy, this is 
incorrigible stupid and amaturish. I understand what they want - but the 
implementation sucks.


Anders Wallenquist

> Alan.
> _______________________________________________
> Mailing-List:
> Post to:
> Unsubscribe:

Post to:


Gunnar Wagner | Iris Germanica Ltd. | JinQian Gong Lu 385, 8-201 | FengXian Qu, 201404 Shanghai | P.R. CHINA
+86 159 0094 1702 | +49 (0)176 7808 9090 | skype: professorgunrad |

Post to:



Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28