Closed lboeman closed 1 year ago
@lboeman for the license, I've never been clear if you need to continuously update the year or can just keep the year when the license was originally defined. It would be good to clarify that (assuming there is some official guidance somewhere on MIT licenses for open-source software).
@lboeman for the license, I've never been clear if you need to continuously update the year or can just keep the year when the license was originally defined. It would be good to clarify that (assuming there is some official guidance somewhere on MIT licenses for open-source software).
I believe the copyright date should be updated to reflect the year that the codebase was last updated. I'm not sure if there is official guidance, but that is my understanding. I will note that the changes in this PR were at the request of UofA administration to demarcate the conclusion of the project being hosted there.
Thanks for the feedback. I don't have an issue with changing the year, but good to confirm. I'm going through other open PRs (on this repo and others) and will plan on approving/merging the changes this week.
I forgot to merge this before merging PR #802, which also updated the whatsnew
list to include 1.0.13
. Hence the extra commit to resolve the conflict.
Adds missing 1.0.13 to index, updates license to 2022/Univsersity of Arizona.