← Back to team overview

openerp-community team mailing list archive

Re: Licenses guidelines for OCA modules

 

I put authorship, contributors and copyright info only in __openerp__.py.

On other .py files I just use:
# -*- coding: utf-8 -*-
################################################################
#    License, author and contributors information in:          #
#    __openerp__.py file at the root folder of this module.    #
################################################################

Just my 2 cents.


--
*Alejandro Santana*
alejandrosantana@xxxxxxxxx
· · · · · · · · · · · · · · · · · · · · · · · · · · · · ·

ANUBÍA, soluciones en la nube, S.L.

Plaza Fernando Conde Montero Ríos, 9
36201, Vigo (Pontevedra)

www.anubia.es

[image: anubía_logo_2014_i_o_140x140.png][image:
odoo_logo_odoo_ready_140x140.png] <http://www.anubia.es/>



2015-01-05 13:38 GMT+01:00 Pedro Manuel Baeza Romero <pedro.baeza@xxxxxxxxx>
:

> I see perfect to reduce the overhead of the headers, because it's a
> nonsense, so I would say option b, but a recurring conflicting issue is
> about the copyright: this part doesn't reflect at all the reality of the
> code because:
>
>    - People copy/paste from Odoo code and let Odoo copyright, which is
>    not correct.
>    - Author put its copyright, but contributors (that can exceed the LOC
>    contributed from the author), doesn't remember to put its name in it.
>    - BTW, it's very tedious to maintain this section for each file.
>
> Why don't we just simply remove it? Copyright can be deduced from Git
> history. I know that FSF recommends to put it, but it's that, only a
> recommendation, not a must for AGPL.
>
> Regards.
>
> 2015-01-05 12:09 GMT+01:00 Yannick Vaucher <yannick.vaucher@xxxxxxxxxxxxxx
> >:
>
>> Most developers dislike redundancy, thus, all are tempted to reduce the
>> size of source code by reducing or completly removing redundant license
>> from source files. [1]
>>
>> Moreover, when writing a module you often have py files with only few
>> lines, thus the header takes a lot of place.
>>
>> I think it is time to write down what we can and cannot do about AGPL
>> license.
>>
>>
>>
>> Actual common use is to attach the full header at start of each source
>> file. This is what is recommended by
>> http://www.gnu.org/licenses/agpl-3.0.html
>>
>> To be said I'm completely against removing completely the header I think
>> a minimal copyright must be present in each source file to be read by the
>> one who opens the file.
>>
>> To be minimalist, from what I read there thought, we could also accept
>> minimal header with license like this
>>
>> # Copyright 2015 <author>
>> # <notice where to find full licence>
>>
>> (with full license in __openerp__.py for exemple)
>> Exemple here [2]
>>
>>
>> Our options:
>> a. We keep full header on each source file. And accept only this one.
>>
>> b. We define a minimal header template like this as an altenative (mostly
>> taken from David Beal's proposal):
>>
>> # -*- coding: utf-8 -*-
>> # Author: <author name>
>> # Copyright 2015 <company or author>
>> # License AGPL version 3 or later
>> # See license in __openerp__.py or http://www.gnu.org/licenses/agpl-3.0.txt
>>
>>
>>
>>
>> [1] More talks about it in:
>> https://github.com/OCA/product-attribute/pull/34
>>
>> [2] An exemple of minimal license:
>> https://github.com/OCA/carrier-delivery/pull/35/files
>>
>> Cheers,
>>
>> Yannick Vaucher
>> Business Solutions Software Developer
>>
>> Camptocamp SA
>> PSE A, CH-1015 Lausanne
>> Phone: +41 21 619 10 30
>> Office: +41 21 619 10 10
>> http://www.camptocamp.com/
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References