Remove the date range from KDAB copyrights#596
Merged
Conversation
Keep the file creationYear as part of the copyright but no longer worry about extending the date range to include the currentYear. This standardizes to KDAB copyright policy.
Contributor
|
Thank you or this work. Standard is always useful! Just as a question: What do you think of dual-licensing Hotspot under GPLv2 / GPLv3 (like KDDockWidgets) or license under "GPL version 2 or later" (the license text may be unchanged then), which would allow both license versions for future use (depending on the dependencies, of course)? |
milianw
approved these changes
Jan 17, 2024
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
3 participants
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.
Keep the file creationYear as part of the copyright but no longer worry about extending the date range to include the currentYear.
This standardizes to KDAB copyright policy.