You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docs repo is multi-licensed, MIT and CC-BY-4.0. The README outlines the situation but still many people and most tools (including GitHub's own licensee) will not recognize the current license structure where the two LICENSE files are in separate directories.
What changes are you suggesting?
The licenses should both be at the root in separate files (e.g., LICENSE and LICENSE-CODE). That makes it obvious to the repo browser that there are two licenses and enables licensee (and other tools/systems) to pick up the multiple licenses. There is a separate problem of updating the GitHub UI to deal with multiple licenses appropriately but that can be addressed separately.
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
What is the current behavior?
The docs repo is multi-licensed, MIT and CC-BY-4.0. The README outlines the situation but still many people and most tools (including GitHub's own licensee) will not recognize the current license structure where the two LICENSE files are in separate directories.
What changes are you suggesting?
The licenses should both be at the root in separate files (e.g., LICENSE and LICENSE-CODE). That makes it obvious to the repo browser that there are two licenses and enables licensee (and other tools/systems) to pick up the multiple licenses. There is a separate problem of updating the GitHub UI to deal with multiple licenses appropriately but that can be addressed separately.
The text was updated successfully, but these errors were encountered: