Update copyright #78
Merged
Update copyright #78
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed the copyright was still on 2012.
I sure am not a lawyer, so I don't know how this stuff works at all, but it's my belief that a maintainer should be able to claim copyright for a given year if they were the maintainer for the majority of the year. Based on the timelines of #11 and #42, I think adding the following is reasonable:
Copyright (c) 2018, Victor Titor
Copyright (c) 2019-2020, Kyle Altendorf
One outstanding question is what to do about the intervening 2013-2017 (inclusive).
CC: @schmir @vtitor @altendky please tell me what to do :)