Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Dist-Zilla CPAN distribution.

Report information
The Basics
Id: 59992
Status: rejected
Priority: 0/
Queue: Dist-Zilla

People
Owner: Nobody in particular
Requestors: ABH [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 4.101900
Fixed in: (no value)



Subject: copyright_year only supports one year
At least in the US you're supposed to type a range of years (or each individual year) that the software was modified. The copyright_year configuration only allows a single year.
Please provide a citation, from a reliable source, explaining that/why a range of years should be given. -- rjbs
Subject: Re: [rt.cpan.org #59992] copyright_year only supports one year
Date: Mon, 2 Aug 2010 16:29:28 -0700
To: bug-Dist-Zilla [...] rt.cpan.org
From: Ask Bjørn Hansen <ask [...] perl.org>
On Aug 2, 2010, at 4:26, Ricardo Signes via RT wrote: Show quoted text
> Please provide a citation, from a reliable source, explaining that/why a range of years should be > given.
Well, it's either year of first publication or it's all the years. The Oppedahl Patent Law Firm says ( http://www.oppedahl.com/copyrights/#notice ): "The date. The copyright date is perhaps the most important trap for the unwary. One of the purposes of the copyright date, under U.S. copyright law, is to assist members of the public in identifying works which are so old that the copyrights have expired. To do this, a member of the public would take the copyright date appearing in the notice, add to it the number of years of the copyright term, and thereby arrive at a conclusion as to when the copyright would have expired. In the case of computer software, it is common place for the work to include original matter from many different dates including original work dating from any of several different years. Consider what would happen if the most recent year were the only year used in the notice. A member of the public would then be led to the conclusion that the entirety of the work is protected by copyright starting from that year and ending at the end of copyright term. But if part of the work dates from a previous year, then its term expires one year earlier than the rest of the work. This could mislead members of the public in the sense that they would incorrectly think that none of the work could be copied until the end of the term that is based on the date in the notice, when in fact part of the work would have entered the public domain one year earlier than the end of that term. There have been court cases where judges have stricken all of the copyright rights in a work due to such incorrect statements in the copyright notice. Because of this, it is wise to ensure that nothing in the copyright notice would mislead the public regarding the end of the copyright term. If only one year is to appear in a notice, it should be the oldest year, associated with the oldest of the matter in the work. In other words, if one must err it should be in the direction of omitting newer years, not older years. Another approach is to put a range of years. For example, if the oldest matter in the work dates from 1991 and if the newest matter dates from 1994, the notice might say copyright 1991 to 1994 and the name of the owner." The US copyright office just asks for "year of first publication". If you follow that, then the current default behavior of using the current year is wrong (as soon as the year changes even for new distributions): http://www.copyright.gov/help/faq/faq-definitions.html#notice In http://www.copyright.gov/circs/circ1.pdf: "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. The year date may be omitted where a pictorial, graphic, or sculp tural work, with accompanying textual matter, if any, is reproduced in or on greeting cards, postcards, stationery, jewelry, dolls, toys, or any useful article; [...]" However it also says: "The year of publication may determine the duration of copyright protection for anonymous and pseudonymous works (when the author’s identity is not revealed in the rec ords of the Copyright Office) and for works made for hire." However: The Apache notice policy asks for the "year(s) of distribution": http://www.apache.org/legal/src-headers.html The gnu guidelines asks for explicitly spelling out each year: http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html University of California says: http://www.ucop.edu/ott/faculty/crbasics.html "Insert the year the work was first published as well as any subsequent years when a modified version is published. Publication is defined in the Copyright Act as the distribution or offer of distribution of a work to the public by sale or other transfer of ownership or by rental, lease, or lending. If the work has not been offered for sale or transfer, it is not published." I think having all the years listed is to get the dual effect of "My stuff is older" and having the length of the copyright extend. - ask
Show quoted text
> "To update the list of year numbers, add each year in which you have
made nontrivial changes to the package." Allowing multiple years would be more accurate for when there are development gaps, which is particularly the case when an old module gets a new maintainer. Although, if that were supported I guess it would be nice to be able to specify separate copyright holders as well... Copyright 2002-2006 A Copyright 2011 B I don't have any good suggestions for how to specify that, though.
Il Ven 05 Ago 2011 18:19:32, RWSTAUNER ha scritto: Show quoted text
> > "To update the list of year numbers, add each year in which you have
> made nontrivial changes to the package." > > Allowing multiple years would be more accurate for when there are > development gaps, which is particularly the case when an old module gets > a new maintainer. > > Although, if that were supported I guess it would be nice to be able to > specify separate copyright holders as well... > > Copyright 2002-2006 A > Copyright 2011 B > > I don't have any good suggestions for how to specify that, though.
Even though it might seem like a shameless plug, I'd suggest to take a look at Dist::Zilla::Plugin::CustomLicense.
My practice is to always use the oldest year only, and it is what I recommend. A solution like CustomLicense is what I recommend for those who feel strongly about having more detailed information. I can't give you a specific piece of advice on how to configure it, but I will definitely do work needed to allow it to work correctly with DZ — but not work to make DZ natively worry about anything more than "I have a license that can be stringified." -- rjbs