Community mailing list archives
Re: Odoo v9 Community and Enterprise editionsby
On 11/05/15 21:08, Fabien Pinckaers wrote:
<blockquote cite="mid:CANRftat0jWRUC=94TAS9M7VZ=+SxHLvT_83JrfNdcnNQkXaSdw@mail.gmail.com" type="cite">It is perfectly possible for Odoo to have a license that clarifies the meaning of "linking" in the particular context and the intent of any viral nature of anything going on. Wordpress got some clarification around themes and plugins: https://wordpress.org/news/2009/07/themes-are-gpl-too/ which is a similar situation.Joël,
=> 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!
My feeling is that modules are a derivative work of Odoo core, but Odoo core is not a derivative of the modules, and modules are not typically derivatives of other modules (unless they extend each other)
<blockquote cite="mid:CANRftat0jWRUC=94TAS9M7VZ=+SxHLvT_83JrfNdcnNQkXaSdw@mail.gmail.com" type="cite">not sure I would make it OCA specific, or put the onus on OCA to make any statements, my suggestion would be to have a license field on the ir.module.module object and for AGPL licensed modules have a mechanism for downloading a zip of that currently running module. Secondly, forbid module dependencies that are incompatible with the license, so Odoo would not allow a non-AGPL module to depend on an AGPL module. This way compliance with the AGPL source code availability just works, even if you tweak the code and the intent of the AGPL is preserved - it stays free and open.
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 ifthe instance contains non AGPL compatible modules. But OCA does not accept thatsomeone 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.
<blockquote cite="mid:CANRftat0jWRUC=94TAS9M7VZ=+SxHLvT_83JrfNdcnNQkXaSdw@mail.gmail.com" type="cite">
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)