Community mailing list archives
Re: FW: access to code under AGPL v3by
Please someone correct me if I'm wrong on this:
- The Copyright is attached to authorship: it belongs to Authors only.
- The OCA did not author a single line of code and has no Copyright on the OCA modules.
- It does have special *(re)licensing rights* on the code granted by the Authors through the CLA.
Thus, IMHO it is incorrect to write the OCA as the copyright holder in the modules.
As a hoster, if you are installing AGPL modules from the OCA, you are fine. If you are installing the same module from a contributor, then this contributor can take action for license infringement.
First, he would have to inform the user, which would inform you. At this step, your customer and you can decide to :
- switch to install and use the module from the OCA, and your customer and you will be fine;
So the recommendations I give is to use OCA modules because the OCA decided to protect the user. If a user uses the contributor version of the module, he doesn't have the long term guarantee that this module and its future versions will remain available under an OSI compatible license. The contributor can decide to close it when migrating to version 9, for example.
- remain on his version and then he can sue your customer, who can sue you.
"he doesn't have the long term guarantee that this module and its future versions will remain available under an OSI compatible license"
About AGPL + Proprietary, it can be read from the license that only "subprograms that the work is *specifically designed to require*" are covered.
This is the support for the interpretation that AGPL can run alongside Proprietary as long as it's not designed to require it.
If an Odoo module is well constructed, it translated to not having a AGPL module depend on Proprietary ones.
In my (informed but personal) opinion, everything points for that being correct.
But there is not 100% consensus on this, of course. Some wordings of the AGPL don't have direct translation to Python programs.
So, IMO the OCA statement was just to publicly ensure everyone that they share this interpretation.
To be clear there is no such thing as a special OCA AGPL license - all OCA modules must have an unmodified OSI approved license, the AGPL is the one recommended and used by default by contributors.