Community mailing list archives

Re: Odoo v9 Community and Enterprise editions

Camptocamp SA, Joël Grand-Guillaume
- 05/12/2015 05:46:52

I think we may have various options, but I'm not sure any of them are really alright. I agree to investigate those options and see how it goes. Let's try to gather informations on the topic and have a talk on it during Odoo Experience. On the possibility to explore:

 * Add an exception clause to the AGPL license within the OCA to allow to install them along with paid apps from Odoo Enterprise

 * Add an exception in the LGPL of Odoo core that clarifies the meaning of "linking" in the particular context and the intent of any viral nature. Wordpress got some clarification around themes and plugins: which is a similar situation (thanks Allan) or this thread : (thanks Daniel)

That being said, you must understand the OCA will never change any license without the express consent of their contributors and members. It is not up to the OCA to decide, so even if a solution is found, but no-one wants it among our contributors and members, we'll respect their choices.

Now my personal opinion is that if we can find a compromise here, everyone would probably be happy with that as long as the AGPL stays in place. I personally can live and be happy with my modules allowed along side with yours if they're still AGPL.



On Mon, May 11, 2015 at 10:07 PM, Fabien Pinckaers <> wrote:

   => It seems that may be, if no OCA module extend a private apps AND no private apps extend OCA module, the viral clause of the AGPL doesn't apply. If that's true => End of the story, there is no more trouble.

That would be a good solution for everyone. It fits OCA needs, the interest of the users and Odoo SA needs.

If it's possible, that's great!

I think its the solution we should investigate. Even if it does not work at the license level, this may be fixed by an addendum to the license or a public statement. It woud look like:

    "Despite the AGPL restrition, OCA publicly allow any Odoo user to use OCA apps, even if
    the instance contains non AGPL compatible modules. But OCA does not accept that
    someone develops a non open source modules that depends on an existing OCA module"

The "Despite the AGPL restrition" clause may not even be necessary. (I don't think so, but let's check) We have to find a way to make it legal, but it looks like it satisfies everyone interest.

At least we share a common direction. We just need to find a way to legalize it. --> I propose to discuss the final solution at the community days.

Note that you should have see to that before starting this thread ;)

Have a look at the thread, I answered to Eric's thread that announced incompatibilities between Enterprise and OCA. I answered by proposing a solution to collaborate VS a competition (your solution would do the same result if its possible)


Post to:



Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28