Community mailing list archives
Re: Enterprise: Is it allowed to use AGPL community modules?by
Lambda Networks AS, Levent Karakaş
This discussion has been made mostly on our side, let's see how it feels like if we put on customer shoes.
Assume a case that a partner develops proprietary code over enterprise version and customer buys this with a similar clause as odoo sa's (have to pay forever or remove the applications). What if customer has problems with partner? Trapped inside another trap....
Similar case: partner (official or else) develops proprietary code over community version and sells it to a customer. Later they want to finish working together. How will the customer get out of this situation?
What is the exit strategy here? How do we explain this to customer while selling it?
2015-10-06 13:23 GMT+03:00 Dominique Chabord <firstname.lastname@example.org>:
2015-10-06 11:49 GMT+02:00 Alan Bell <email@example.com>: > > > On 05/10/15 19:19, Dominique Chabord wrote: >> Do you admit this agreement doesn't engage authors of modules which is >> not copy-righted by OCA ? >> It is all what this thread is about, I think. > so, what would your interpretation of the license be? That you can't > install your AGPL module on an Enterprise install? you got the point, or someone cannot install Enterprise with my module if I don't want it. If I'm not a partner, my open-source business is protected : - against partners who would get Enterprise capability and - against other players who might integrate my work in their proprietary product. and I can sell dual licensing. So depending on which category you stand, you get conflicting interests but the license cannot be read differently. This is what OCA said also and why they granted additional rights to users for all the modules for which they share the copyright. If AGPL were permissive, they wouldn't have to. > If so, clarify that > is your intent in your license file and then re-read freedom 0 > http://www.gnu.org/philosophy/free-sw.html The license is self sufficient and shouldn't never be modified if you foresee to enforce it some day. Anyway, some already followed your recommandation and precised in the code they don't accept any loose interpretation. As a general rule, if you apply licenses strictly, you have a lower legal risk. Don't go against authors' will and you are quite covered. Since you refer to gnu.org project, which Odoo is not part of and historically couldn't be, I can't resist to tease you with this page : http://www.gnu.org/licenses/why-not-lgpl.html ;-) > > Alan. > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: https://www.odoo.com/groups?unsubscribe