Contributors mailing list archives


Re: Enterprise dependencies

Landis Arnold
- 18/10/2016 10:10:17
I recommend not mixing into Odoo Enterprise.  A different approach would be generating Community Modules that do, generally, what Enterprise modules do.

Many people, myself for one, do not want to give bandwidth to the Enterprise universe.  It feels a trap with no escape.
Better to encourage Enterprise to open itself to the Community rather than the community to close itself to the enterprise.

Magento it seems, has navigated this conundrum ok, but not with regards to requiring "open software" in modules they list in their directory

Joomla has done better by allowing "charge for service/consult" but absolute insistence on Open Source builds if, at a minimum, they are to list Modules and Components from 3rd Parties in their library.

My opinion only.  Not a statement of absolute truth or anything else.

Best regards and thank you all.

Landis Arnold
Nomadic, Inc.
Boulder, CO USA

From: "Alexandre Fayolle" <>
To: "Contributors" <>
Sent: Tuesday, October 18, 2016 2:53:54 AM
Subject: Re: Enterprise dependencies

Technically not an issue, but legally yes. Currently the OCA does not
have access to odoo/enterprise.


On 18/10/2016 10:38, Eric Caudal wrote:
> I was under the impression that the module LGPL you create can work on
> EE without special license (the module is independent per se).
> Question of runbot is a good one but nothing would prevent to have a
> runbot with EE module: it should be discussed of course (and agreed in
> the OCA whether this is a good idea) and agreed with Odoo for access of
> the code but technically not an issue.
> --
> *Eric Caudal* /[Founder and CEO]/
> Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211
> 8017/27/37 (Office)
> *Elico Shanghai* (Hong Kong/Shenzhen/Singapore) 
> /*Odoo Gold Partner // Best Odoo Partner APAC 2014 and 2016*/
> On 10/18/2016 03:53 PM, Daniel Reis wrote:
cite="" > type="cite"> > > I'm not sure wjhat we mean with "related to EE". > If it is "it is designed to depend on", AFAIK you can't have LGPL > modules depending on Proprietary ones. > I have the idea that once you have one Proprietary module in your stack, > everything upward (depending on it) is also proprietary. > > Regarding the OCA, open source is built into it's mission and bylaws. > IMHO Proprietary is out of scope, to say the least. > In practical terms, I agree with Stephan: the OCA has no access to Odoo > EE and is unable to provide services such as Quality Assurance for EE > modules. > > But if those modules are built in such a way that they don't require EE > to work, then it's business as usual, and they can fit nicely into OCA. > > -- > Regards > Daniel > > > Citando Stefan Rijnhart : > >> On 10/18/2016 02:53 AM, Eric Caudal wrote: >> > >> > Hi Ondrej, >> > >> > No problem to host LGPL modules in OCA, even related to EE. You might >> > want to specify it in the README file but there is absolutely no >> > restriction as long as the license is open source. >> > >> >> Wondering about the legal possibilities of having these modules tested >> against the EE. Otherwise, it will be difficult to maintain the quality >> control or even getting enough people to review these modules. >> >> Regards, >> Stefan. >> >> _______________________________________________ >> Mailing-List: >> Post to: >> Unsubscribe: >> > > > > _______________________________________________ > Mailing-List: > Post to: > Unsubscribe: > > > _______________________________________________ > Mailing-List: > Post to: > Unsubscribe: > -- Alexandre Fayolle Chef de Projet Tel : +33 4 58 48 20 30 Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac Cedex

Post to: