Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

loosen the constraint on copyright_year #135

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
5 participants
Contributor

book commented Dec 26, 2012

given that the value is inserted in a string, and not used in any
computation involving integers, it seems nice to give authors the
option to declare a range of years is they wish to, such as

copyright_year = 2010-2012
loosen the constraint on copyright_year
given that the value is inserted in a string, and not used in any
computation involving integers, it seems nice to give authors the
option to declare a range of years is they wish to, such as

    copyright_year = 2010-2012
Contributor

karenetheridge commented Apr 28, 2013

I'm planning on making some changes/improvements to copyright year handling (along with some related changes to App::Software::License) that will make ranges a little more natural -- poke me again in a while.

Contributor

dolmen commented Jul 24, 2013

From http://www.copyright.gov/circs/circ01.pdf page 4, it mentions about date in the copyright notice:

The year of first publication of the work. In the case of
compilations or derivative works incorporating previously
published material, the year date of first publication of
the compilation or derivative work is sufficient.

As "the year date of first publication of derivative work is sufficient", the year of the release time should be enough. But IANAL.

So I don't see a reason to change the rule.

dmcbride commented Jan 6, 2014

Olivier, you haven't met my corporate lawyers. First and latest years of copyright are desired, so I'd second this.

Contributor

karenetheridge commented Jul 30, 2014

+1. I've forgotten what I knew about license handling, so if anyone else can remember, please speak up. :)

Presumably we don't need both a starting and ending year in Dist::Zilla, as we can use copyright_year for the start year and assume now is the end year.

Karen,

That may not be sufficient. If the file has not (yet) been changed this year, the continuous/nightly builds may continue to run, and the copyright date should not change until an actual code change is made.

So, while that assumption may be valid for many cases, especially CPAN modules, being able to make it explicit can fulfil certain corporate requirements.

Contributor

book commented Aug 20, 2014

One option would be to allow a special string to mean "current year".

Owner

rjbs commented Jul 25, 2015

Thanks, applied.

WITH A SOUR LOOK ON MY FACE

😊

@rjbs rjbs closed this Jul 25, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment