a) As long as we are consistent, Copyright lines don't conflict. The only
chance they do is if you have one long lived branch, and a file was created
in 2012, in one long lived branch it gets updated in 2013, and then in the
other it is updated again in 2014 and then you merge that long lived branc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As we're on copyright headers topic, is there a clear policy what
headers to use for contributed code, like the one Joyent did or
CloudSigma ?
Should it be:
// Copyright 2014 Canonical Ltd.
// Copyright 2014 CONTRIBUTOR-XYZ..
// Licensed under the AG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4.09.2014 00:54, David Cheney wrote:
> I think this is needless busy work, I vote that as long as there is
> a copyright header with _a_ year, that is sufficient.
>
+100
Let's not do that please, it's pointless.
> On Thu, Sep 4, 2014 at 7:50 AM,
On Thu, Sep 4, 2014 at 5:50 AM, Ian Booth wrote:
> Hi folks
>
> The question recently came up in reviews as to whether we should be
> updating the
> date in the copyright statement in the file header when we make a change
> to the
> code in that file. I sought clarification from Robie Basak, who
I've been asking for updates in my reviews. I'm happy to stop if the
consensus is we don't need to. Once we get an agreement on policy, let's
put it in the style guide.
On 04/09/14 09:55, Gustavo Niemeyer wrote:
I suggest not updating it. Updates on the same line will conflict, and
cause comp
I suggest not updating it. Updates on the same line will conflict, and
cause completely unnecessary headaches. These files are under revision
control, so there are better proofs of when it was changed than just
that header. Then, in a decade or two, if somebody cares, update them
all at once.
On W
I think this is needless busy work, I vote that as long as there is a
copyright header with _a_ year, that is sufficient.
On Thu, Sep 4, 2014 at 7:50 AM, Ian Booth wrote:
> Hi folks
>
> The question recently came up in reviews as to whether we should be updating
> the
> date in the copyright sta
Hi folks
The question recently came up in reviews as to whether we should be updating the
date in the copyright statement in the file header when we make a change to the
code in that file. I sought clarification from Robie Basak, who previously had
provided input on licensing issues and compliance
