hi,
if I understand the request, Nevertheless, I'm not sure the current
period is the best one to modify anything about licence and copyright
notices, as it can become a hot topic soon.
my 2cts only.
___
Mailing list: https://launchpad.net/~openerp-commu
Hi all,
short update from my side, as thinking about this topic.
I recommend:
A) Using Full Header as GNU Recommended
or
B) Using SPDX-License Header.
This is new in Open Source and maybe will make its way.
Frederik did already some research with that and we can scan complete
projects of licen
> 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
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 actua
> 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 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 e
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
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: https://
Hi,
Yannick's proposal remains quite minimal and seems compliable with some
"standard".
But, does it need to contain the copyright info? That is the main point
that keeps hard to maintain: every file with copyright and authorship (and
its related issues like collaborations).
So, could this:
# -*
This is a good idea to follow some standard.
However, SPDX meta tag "SPDX-License-Identifier" is not yet widely used.
It seems that it was firstly used by U-boot project
https://github.com/linux-sunxi/u-boot-sunxi/commit/1a4596601fd395f3afb8f82f3f840c5e00bdd57a
AFAICT it is still under draft pro
On 01/05/2015 06:09 AM, Yannick Vaucher 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]
[snip]
> To be said I'm completely against removing completely the header I
> t
I think you see it not so simple. The basic shipment unit of code is
always a file. Not a module nor a git repositories.
And if you can have modules with libs include with other license you
want pretty see the kind of each class.
So we don't need not to reinvent the wheel. Just stick to GNU best
pr
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 <
leart...@gmail.com> wrote:
> I agree with Pedro. Copyright noti
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
Avoiding heavy characters case is perfectly fine, better indeed and less
stress for the eyes.
Alejandro Santana
alejandrosant...@anubia.es
~
ANUBÍA, soluciones en la nube, S.L.
www.anubia.es
El 5/1/2015 15:59, "Sandy Carter"
escribió:
> Avoid the # box, I find it very irking to have that many h
Avoid the # box, I find it very irking to have that many heavy
characters like that.
Besides: E265 block comment should start with '# ' (single space after
the first hash).
How about:
# -*- coding: utf-8 -*-
#
# License, author and contributors information in:
# __openerp__.py file at the root f
Le 05/01/2015 12:09, Yannick Vaucher a écrit :
b. We define a minimal header template like this as an altenative
(mostly taken from David Beal's proposal)
I think this is the simplest option. I'd even drop line 2 "# Author:
".
We should also not put the licence in __openerp__.py but rather in a
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 fo
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
19 matches
Mail list logo
