Skip to content

Conversation

@MattsonCam
Copy link
Member

Updated the playbook by mentioning year ranges in copyright notices, and giving an example.

Updated the playbook by mentioning year ranges in copyright notices
Copy link
Member

@d33bs d33bs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

![Process for choosing a repository license.](images/selecting_a_license.png)
According to the [CU Innovations office](https://www.cuanschutz.edu/cu-innovations) when creating or modifying a license you must include the following line (with the appropriate year):
`Copyright (c) <year> the Regents of the University of Colorado`
If the copyright includes a range of years it is best practice to include this range in place of a single year: `<first_year>-<last_year_developed>`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with this sentiment and just the same thought it might help to strengthen this with a citation. Is there a reference we could add here to help bolster the strength of this statement?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is what I gathered from chatgpt, also Mike supplied this resource but it seems to focus on blogs and websites (https://www.copyrightlaws.com/copyright-symbol-notice-year/). Maybe I'll try looking for another resource

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants