Members mailing list archives

members@odoo-community.org

Re: Licence Change of OCA Modules

by
Groupement Régional Alimentaire de Proximité, Sylvain LE GAL
- 04/03/2015 16:44:53
Hi again

Excuse me if I was not clear.
1/ I just want to make sure that code I shared / I'll share to OCA will not be relicensed without democratic discussions and votes ;

2/ In your link (http://odoo-community.org/blog/news-1/post/odoo-relicensing-11), we can read :
"For future contributions, we think every contributor should be able to choose the license under which he wants to release his code. The OCA will accept modules released under any of the OSI approved license compatible with the OCA code base".
I so don't understand why there is an AGPL LICENCE file in root folder of each OCA repository as it could contains modules written under various licences ;

Kind regards.

Sylvain LE GAL
Service informatique
GRAP - Groupement Régional Alimentaire de Proximité

3 Grande rue des Feuillants, 69001 Lyon
Bureau :
(+33) 09.72.32.33.17
Astreinte :
(+33) 06.81.85.61.43
GRAP sur le Web : Site Web | Facebook | Twitter
GRAP - service Informatique sur le Web : Twitter


2015-03-04 17:07 GMT+01:00 Leonardo Pistone <lpistone@gmail.com>:
Hi,

if you see the last official post on the subject,
http://odoo-community.org/blog/news-1/post/odoo-relicensing-11 ,
the OCA board has decided to not relicense any of its modules, but to
accept contributions in some other ones.

I personally agree with that decision, as I too feel that there is no
need to go through a license change for OCA.

On Wed, Mar 4, 2015 at 4:00 PM, Sylvain LE GAL <sylvain.legal@grap.coop> wrote:
> Hi All,
>
> The last months, community members talked a lot about licences, due to the
> change of licence of Odoo SA from AGPL to LGPL.
>
>
> I so thought about the possibility to change the licence of OCA modules. In
> the time being :
> - Contributors sign a CLA that allow OCA to change the licences;
> - OCA allows OSI licences. (AGPL, LGPL, BSD, MIT, ...) ;
> - In fact, all modules are under AGPL licence; (see below) ;
>
>
> I consider that the licence change is an important decision, I would like to
> propose to add in the OCA bylaws the following rule :
> "The decision to change licences of OCA Modules must be only done in general
> assembly and validated by X% of the members", X must be something like 2/3.
> (or something similar, written in correct english) ;-)
>
> What do you think about that proposition ?
>
> Thanks for your attention.
>
> Kind regards.
>
>
>
> 'licence' value
> (in __openerp__ file)
> Unported Modules Ported Modules
> AGPL-3 189 172
> AGPL v3 12
> GPL-3 2 4
> GPL-2 or any later version 4
> GPL-3 or any later version 9 4
> Undefined 24 36
>
>
>
> Total 240 216
>
>
>
> Ratio Ported Module / Total
> 47,37%
>
> Analyse of all OCA modules presents in Github, based on default branch
> (usually '8.0), realized 2 weeks ago.
>
> Sylvain LE GAL
> Service informatique
> GRAP - Groupement Régional Alimentaire de Proximité
> 3 Grande rue des Feuillants, 69001 Lyon
> Bureau : (+33) 09.72.32.33.17
> Astreinte : (+33) 06.81.85.61.43
> GRAP sur le Web : Site Web | Facebook | Twitter
> GRAP - service Informatique sur le Web : Twitter
>
> _______________________________________________
> Mailing-List: http://odoo-community.org/groups/members-4
> Post to: mailto:members@odoo-community.org
> Unsubscribe: http://odoo-community.org/groups?unsubscribe

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