Community mailing list archives

Re: access to code under AGPL v3

Libertus Solutions, Alan Bell
- 01/08/2016 08:06:38

On 08/01/16 12:29, André P. wrote:
<blockquote cite="" type="cite">

> 1/ If I make an installation for a customer, he (the final customer) could get a mail from anyone requesting the code used in his instance?

Yes. Provided that this anyone as, at least, access to the login page.

Really? Accessing the login page counts as a "user" of the software? That seems a little extreme.
it also falls into the category of "not going to happen".

This is a rather academic discussion, but yes, anyone with access to the system can in theory request the source code - which you can charge an administration fee for doing if you give it to them on a disk. It is rather pointless because random people wouldn't do that, they would go get it from github.
(1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.

The point of the AGPL is so that you can't start with Odoo, extend it with some secret stuff and provide a SaaS platform based on Odoo+secrets that other people can't also offer, and customers couldn't take in-house or elsewhere if they wanted to.

If you are doing Odoo without secret stuff, or your unpublished changes to the code are not a massive secret as such, but are of no interest to anyone but yourself (for example in one system I added a field to record the moisture sensitivity of stocked electronic components, it isn't a secret, but hardly anyone else would care about that feature) then you don't need to be concerned.