← Back to team overview

openerp-community team mailing list archive

Re: Licenses guidelines for OCA modules


Also agree to option b. Not to mention that if there should be an update to
license it must be done in each and every .py file which is kind of
nonsense and very impractical

On Mon, Jan 5, 2015 at 5:21 PM, Leonardo "LeartS" Donelli <
learts92@xxxxxxxxx> wrote:

> I agree with Pedro. Copyright notices are bad/useless
>  - Often outdated and incorrect (because copy pasted without
> modifications, for example)
>  - Don't (can't) reflect the complicated situation of OCA modules
> autorship/contributions
>  - useless from a legal point (see:
> http://hackerboss.com/get-rid-of-templates/), copyright is implied by
> autorship (which is better determined using git) and does not need to
> be explicitly declared.
> Regarding the LICENSE, despite what the FSF says, I think than putting
> it in a LICENSE file is enough for all practical and theoretical
> purposes. Just look at some big open source projects source code.
> A nice read:
> http://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html
> _______________________________________________
> 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