Contributors mailing list archives
Re: Right way to do a new OCA module that depends on EE's LGPL module.by
Acsone SA/NV, Stéphane Bidoul
> I have checked that "approvals", although in EE source code, its license is in CE, LGPL.
Have you checked that with Odoo ? Some EE modules don't have a license key, and when you load them in a database, the license field of ir.module.module defaults to LGPL.
But last time I reported that to Odoo it was quickly fixed.
So unless explicitly written otherwise I would assume that all the odoo/enterprise repo is under a proprietary license.
And you can't create a module that depends on both AGPL and proprietary code.
In any case adding code that depends on Odoo EE in OCA is not possible because the EE code is not public so we could not run CI, runbot etc.
On Mon, Jan 25, 2021 at 4:32 AM Kitti Upariphutthiphong <email@example.com> wrote:
Dear community,Got some questions about licensing.There are modules that we want to extend but they are in EE14 --> "approvals", "approvals_purchase".Where approvals is a simple module for approving something. And approvals_purchase allow creating purchase order at the end of process.
They are quite simple. But what we need is to create modules "approvals_purchase_request" and "approvals_hr_expense".I have checked that "approvals", although in EE source code, its license is in CE, LGPL.What is the right way to deal with this?
- Just include approvals in OCA and continue the new module (as it is LGPL, not sure)
- We can't use "approvals", and so, we have to first create something similar to it, may be renaming it, add/remove some feature etc. and make it pure OCA module first before continue our needing module.Thank you!Kitti U.
Ecosoft Co. Ltd., Kitti Upariphutthiphong