Skip to content

Bump copyright year to current release year #75

New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

paultcochrane
Copy link
Contributor

While looking through the README I noticed that the copyright year
didn't match the year of the most recent release. This commit updates
the values to match each other.

This PR is submitted in the hope that it is useful. If you want anything changed, please just let me know and I'm more than happy to update it and resubmit as necessary.

One thing that I was wondering: is the copyright holder still correct? Is Giles Aas still the copyright hoder, or should this be extended or changed in some way?

While looking through the README I noticed that the copyright year
didn't match the year of the most recent release.  This commit updates
the values to match each other.
@karenetheridge
Copy link
Member

IMHO the copyright year is fine left at the starting year, so it doesn't need to be adjusted every year, but others may disagree.

@oalders
Copy link
Member

oalders commented Jan 5, 2022

Is Giles Aas still the copyright hoder,

Yes, I think that's the most appropriate option here.

@@ -3,7 +3,7 @@ author = Gisle Aas <gisle@activestate.com>
license = Perl_5
main_module = lib/Net/HTTP.pm
copyright_holder = Gisle Aas
copyright_year = 2001-2017
copyright_year = 2001-2021
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this PR could consist of just a change to this file. The others will be generated on dzil release. I would suggest copyright_year = 2001 so that we don't need to keep the range up to date annually.

@oalders
Copy link
Member

oalders commented Jan 21, 2022

Thanks for pointing this out, @paultcochrane . I've fixed it via 83119b8

@oalders oalders closed this Jan 21, 2022
@paultcochrane
Copy link
Contributor Author

Thanks for handling this @oalders! My apologies for not having replied sooner; my tuits outside of work have been very limited recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants