Contributors mailing list archives

contributors@odoo-community.org

Re: Licence of version 9.0 modules

by
ThinkOpen Solutions Portugal, Daniel Reis
- 15/09/2016 23:24:45

João,

First, IANAL, and as far as I understand, the key is the definition for "Corresponding Source" in the first article of the AGPL:

The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.


The (A)GPL requirement is a conceptual one: that all the code *needed* to run your AGPL code is also AGPL.
The point is that you must have access to all sources necessary to run it.
For Odoo modules, the code needed would usually be it's dependencies.

This means that unrelated code is not contaminated by AGPL.
Running it in the same memory space criteria has adherence with the license text.
Accidental coexistence of code is not relevant; intention/need to use that code is needed.

Less obvious, you're also allowed to replace one on the AGPL dependencies with a non-AGPL one, for a particular code distribution.
Odoo SA did this with the `web` module: you coudl use the Enterprise Web module with AGPL web modules, because these AGPL modules would also work using the AGPL CE version of the web module.

See also: https://www.gnu.org/licenses/gpl-faq.html#FSWithNFLibs.

--
Daniel


Citando Joao Alfredo Gama Batista <joao.gama@savoirfairelinux.com>:

Hi all,

 

It has been a great discussion so far and I understand the OCA recommendation but I'd like to concentrate on the specific point regarding the possibility or no to use AGPL with closed source modules since the OCA interpretation in this matter seems a bit simplistic to me.

 

> Can I run OCA AGPL modules and closed source modules on the same instance?

> Yes, as long as closed source modules do not depend on AGPL ones and respect the license of its dependencies defined in the “depends” key of its manifest file (and vice versa).

 

Imagine the scenario where someone is an integrator and its deliverable is an customized odoo instance/server with LGPL, AGPL and OEEL code (this deliverable we will call "the program"). In technical terms, the moment the person deliver "the program" to it's client and runs it, we will have AGPL and OEEL running in the same memory space which is a situation that AGPL doesn't like (independently of the content of the `depends` keyword).
 
People praised (A)GPL exactly because it "contaminates" all derivative work but it's exactly that characteristic that makes the statement about using it in a project with OEEL modules inaccurate and hard to sustain.

 

(Of couse this is all my personnal opinion based on my research and I might be wrong)

 

I think that's the remaining ambiguity.

 

Best regards,
 
Joao Alfredo Gama Batista
Consultant en Logiciel Libre
Savoir-faire Linux inc.
joao.gama@savoirfairelinux.com
+1 514 276-5468 poste 163
 
De: "Ray Carnes" <ray.carnes@bistasolutions.com>
À: "Contributors" <contributors@odoo-community.org>
Envoyé: Mardi 13 Septembre 2016 17:08:15
Objet: RE: Licence of version 9.0 modules
 

I wasn’t aware of remaining ambiguity.

 

 

 

 

 

https://odoo-community.org/blog/oca-news-1/post/oca-odoo-meeting-on-licenses-21

 

 

 

 

 

Can I run OCA AGPL modules and closed source modules on the same instance?

 

 

Yes, as long as closed source modules do not depend on AGPL ones and respect the license of its dependencies defined in the “depends” key of its manifest file (and vice versa).

 

 

 

 

 

 

 

From: David Dufresne [mailto:david.dufresne@savoirfairelinux.com]
Sent: Tuesday, September 13, 2016 1:54 PM
To: Contributors <contributors@odoo-community.org>
Subject: Licence of version 9.0 modules

 

 

 

 

Hi contributors,

 


 

 

Many modules on OCA are still published under AGPL-3 for Odoo 9.0.

 


 

 

I am wondering if anyone planned to mass commit the licence to LGPL-3.

 


 

 

This would remove all ambiguity regarding whether the OCA modules are compatible or not

 

in an Enterprise deployment.

 


 

 

Thanks

 


 

 

David Dufresne, Consultant en logiciels libres

 

Savoir-faire Linux

 


 

 

Téléphone  : 418-525-7354 #156

 

Cell       : 418-271-0915

 

Ring ID    : 9ac472765d298cc5de294b5765d0ccfaec48cbbf

 

www.savoirfairelinux.com

 


 

 

ISO 9001 et ISO 14001

 

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

 

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe