Add in Crown Copyright #243
Merged
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
There was a problem hiding this comment.
Just the date to update I think. The issue #178 is to do with clearer guidelines for copyright statements in the code itself so is seperate (though the "first published" advice may stand there too...)
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.
The copyright notice should say Crown Copyright. This updates the template the same way we do in the common Fortran template and LFRic Core repos.
I'm not sure if this is what Rich was referring to in #178 but I have removed the code which updates the year in the copyright as you normally only add years with major revisions and shouldn't really remove the year the docs were first published. Happy to clarify with legal on this if needed.