[New Best Practice Guide]: LICENSE
riverma opened this issue · comments
Checked for duplicates
Yes - I've already checked
Describe the needs
We need a guide to document institutionally authorized ways to work with popular licenses such as Apache V2 and MIT while respecting institutional copyright / markup language.
Some possible paths forward:
- Provide examples of licenses that include institutional markup in a place within the license that doesn't break GitHub's license validator
- Recommend separation of LICENSE and COPYRIGHT information into separate files to hold the info separately (but figure out how to deal with copyright language within the license that ships with it)
Thank you @riverma! I don't know why we didn't simply make this a ticket previously.