1. Mailing Lists
  2. Contributors
  3. Re: Licence of version 9.0 modules

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Licence of version 9.0 modules

Re: Licence of version 9.0 modules

Avatar

Re: Licence of version 9.0 modules

by
ClosingAp Open Source Integrators Europe, LDA, Daniel Reis
- 16/09/2016 10:50:19

Hi Frederik,

I read the AGPL closely several times, and have a hard time to see why an Odoo module should contaminate other unrelated modules, not needed for it to function.
By "unrelated I mean "not specifically designed to require" by the AGPL licensed module.

IMHO the "system library" is not even needed to protect unrelated code from AGPL contamination.
But it reinforces the idea that AGPL should allow contaminating unrelated code is not in the spirit of the

So I would like to learn more aboue the opposite point of view:
Can you elaborate on your interpretation of the "corresponding source" definition?
Should the "not specifically designed to require" text not apply for the case of Odoo modules?


Regards
Daniel

 


Citando Frederik Kramer <frederik.kramer@initos.com>:

Hi Pedro, 

i think this is the crucial point. It's not Odoo or the OCA but somebody
that wants to have the case clarified at court that puts the thread on
us. My honest opinion is that Odoo as well as OCA interpret the AGPL
wrongly by stating that any AGPL module does not infect all Odoo but i
am just a part time scientist and no lawyer. Yet all lawyers i have
spoken to, and i explained the situation agreed on my perspective (maybe
i biased them ;-). However, i think if somebody starts to sue, this will
have a very negative impact on the ecosystem.

Kind regards

Frederik 

Am Freitag, den 16.09.2016, 08:08 +0000 schrieb Pedro M. Baeza
(Tecnativa):
> Actually, this is only a theorization of how to interpret the license.
> Both Odoo and OCA board agreed to interpret the license in the library
> manner, and there are strong facts that supports this, so, no, Odoo is
> not needed to be entirely AGPL.
> 
> 
> But until the first sue with a judgment that creates jurisprudence
> (and this can even vary by countries), there's nothing totally clear.
> Said that, I can't think now in too much interest in breaking this
> license agreement/balance by any of the parties.
> 
> 
> Regards.
> 
> 
> 2016-09-16 9:38 GMT+02:00 Jairo Llopis <jairo.llopis@tecnativa.com>:
>         OTOH, if we consider Odoo a library, then it is perfectly
>         possible to combine them:
>         http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
>         
>         
>         -- 
>         Jairo Llopis
>         
>         _______________________________________________
>         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
> 
> 
> 

-- 
Dipl.-Wirt.-Inf. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dipl.-Wirt.-Inf. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/205/21518
USt-IdNr.: DE815580155

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


 

Reference