You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by Daniel Shahaf <d....@daniel.shahaf.name> on 2020/04/23 15:16:13 UTC
Can 1.10.x claim 2020 copyright? (was: svn commit: r1876864 - /subversion/branches/1.10.x/STATUS)
stsp@apache.org wrote on Thu, 23 Apr 2020 07:08 +00:00:
> +++ subversion/branches/1.10.x/STATUS Thu Apr 23 07:08:37 2020
> @@ -46,6 +46,13 @@ Candidate changes:
> + * r1874850
> + Update copyright year to 2020.
> + Justification:
> + The future is here!
> + Votes:
> + +1: stsp
Between 2020-01-01 and 2020-04-22 this branch received exactly one
commit that touched files other than STATUS. That commit, r1876072,
was done in 2020, but it consisted of a conflict-free merge of commits
from 2019.
I'm not sure if under these circumstances we're actually able to claim
2020 in the copyright notice. Perhaps we are allowed to claim 2020
just because the merge was done in 2020… but then again, perhaps we
aren't. IANAL.
Presumably we'll merge copyrightable commits authored in 2020 before the
next 1.10.x release, which would resolve this concern.
Re: Can 1.10.x claim 2020 copyright? (was: svn commit: r1876864 -
/subversion/branches/1.10.x/STATUS)
Posted by Branko Čibej <br...@apache.org>.
On 23.04.2020 17:16, Daniel Shahaf wrote:
> stsp@apache.org wrote on Thu, 23 Apr 2020 07:08 +00:00:
>> +++ subversion/branches/1.10.x/STATUS Thu Apr 23 07:08:37 2020
>> @@ -46,6 +46,13 @@ Candidate changes:
>> + * r1874850
>> + Update copyright year to 2020.
>> + Justification:
>> + The future is here!
>> + Votes:
>> + +1: stsp
> Between 2020-01-01 and 2020-04-22 this branch received exactly one
> commit that touched files other than STATUS. That commit, r1876072,
> was done in 2020, but it consisted of a conflict-free merge of commits
> from 2019.
>
> I'm not sure if under these circumstances we're actually able to claim
> 2020 in the copyright notice. Perhaps we are allowed to claim 2020
> just because the merge was done in 2020… but then again, perhaps we
> aren't. IANAL.
Probably depends on jurisdiction, but it's immaterial, because ...
> Presumably we'll merge copyrightable commits authored in 2020 before the
> next 1.10.x release, which would resolve this concern.
... just merging this proposed change will make the new copyright year
valid.
-- Brane