As far as I know, copyright is implicitly granted to authors almost
everywhere in the world, so writing the (c) in every file is useless.
Authors can simply use git to prove their rights whenever they need to.
Lionel Sausin.
___
Mailing list:
On Mon, Jan 5, 2015 at 6:09 AM, Yannick Vaucher
yannick.vauc...@camptocamp.com wrote:
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
On 12/01/15 17:01, Ovnicraft wrote:
Here we can do it better, there are some guides about this:
# -*- coding: utf-8 -*-
__author__= Full Name(email)
__copyright__= Copyright (C) YEAR FULL NAME
__license__= AGPL 3.0
__version__= 1.0
So in pythonic way we must add LICENSE file in each
Hi all, and seasonal greatings !
I just released anybox.recipe.openerp 1.9.1, quite a while after
anybox.recipe.odoo 1.9.1
Let me remind you that a.r.openerp supports OpenERP and Odoo versions
from 6.0 onwards, while a.r.odoo is for Odoo only.
A change in policy : at first I'd have preferred
For example, it is quite common that code from other developers, installed on
our customers systems, come to our company to work with. And many times it is
really difficult to discover who are the actual authors, the actual
license(s) (when not in Odoo) and the actual copyright date(s).
On Mon, Jan 12, 2015 at 5:02 PM, Leonardo LeartS Donelli
leart...@gmail.com wrote:
For example, it is quite common that code from other developers,
installed on our customers systems, come to our company to work with. And
many times it is really difficult to discover who are the actual
Here we can do it better, there are some guides about this:
# -*- coding: utf-8 -*-
__author__ = Full Name(email)
__copyright__ = Copyright (C) YEAR FULL NAME
__license__ = AGPL 3.0
__version__ = 1.0
So in pythonic way we must add LICENSE file in each module,
and as best practice
7 matches
Mail list logo
