You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2024/03/05 13:51:00 UTC
[jira] [Comment Edited] (DIRAPI-397) Update Copyright year
[ https://issues.apache.org/jira/browse/DIRAPI-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823626#comment-17823626 ]
Emmanuel Lécharny edited comment on DIRAPI-397 at 3/5/24 1:50 PM:
------------------------------------------------------------------
The proposal to set the upper bound to 'present' should be fine.
Legally speaking (afaik), the upper range is useless. The idea is to 'stamp' the original release, and optionally all the other releases.
What is important is the date from which the copyright applies. So we could perfectly only set the first date (like 2003):
{code:java}
"The copyright notice should include the year in which you finished preparing the release (so if you finished it in 1998 but didn't post it until 1999, use 1998). You should add the proper year for each past release; for example, “Copyright 1998, 1999 Terry Jones” if some releases were finished in 1998 and some were finished in 1999. If several people helped write the code, use all their names.
For software with several releases over multiple years, it's okay to use a range (“2008-2010”) instead of listing individual years (“2008, 2009, 2010”) if and only if every year in the range, inclusive, really is a “copyrightable” year that would be listed individually; and you make an explicit statement in your documentation about this usage."
{code}
(see [The GNU copyright Notice|https//www.gnu.org/licenses/gpl-howto.en.html])
But for clarity, 'present' as an upper bound makes sense.
was (Author: elecharny):
The proposal to set the upper bound to 'present' should be fine.
Legally speaking (afaik), the upper range is useless. The idea is to 'stamp' the original release, and optionally all the other releases.
What is important is the date from which the copyright applies. So we could perfectly only set the first date (like 2003):
{code:java}
"The copyright notice should include the year in which you finished preparing the release (so if you finished it in 1998 but didn't post it until 1999, use 1998). You should add the proper year for each past release; for example, “Copyright 1998, 1999 Terry Jones” if some releases were finished in 1998 and some were finished in 1999. If several people helped write the code, use all their names.
For software with several releases over multiple years, it's okay to use a range (“2008-2010”) instead of listing individual years (“2008, 2009, 2010”) if and only if every year in the range, inclusive, really is a “copyrightable” year that would be listed individually; and you make an explicit statement in your documentation about this usage."
{code}
(see [The GNU copyright Notice|//www.gnu.org/licenses/gpl-howto.en.html])
But for clarity, 'present' as an upper bound makes sense.
> Update Copyright year
> ----------------------
>
> Key: DIRAPI-397
> URL: https://issues.apache.org/jira/browse/DIRAPI-397
> Project: Directory Client API
> Issue Type: Improvement
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Major
>
> Set to 2024
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org