Update copyright notice to reflect current years + pganalyze as author #175
Conversation
This file contains 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
Since this library is now collectively maintained by pganalyze as a company, not just by myself (Lukas), it seems logical to expand the LICENSE file to cover this copyright explicitly.
|
FWIW, as pointed out by Sean in #174 (comment), one generally does not need to do this in the US, as you can't just magically expand your copyright by updating a date. That said, I think for this library it seems reasonable follow Postgres project standard, which is to update the copyright years. (this does not constitute a legal opinion, and we may change this in the future if advised differently by legal counsel) |
msepga
approved these changes
Feb 6, 2023
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.
Since this library is now collectively maintained by pganalyze as a company, not just by myself (Lukas), it seems logical to expand the LICENSE file to cover this copyright explicitly.