Contributors mailing list archives
Re: Enterprise dependenciesby
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
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.
Citando Stefan Rijnhart <firstname.lastname@example.org>:
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.
Post to: mailto:email@example.com