This repository was archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
Add licenses to CommComm repositories #559
Comments
keywordnew
added a commit
to keywordnew/nodejs-collection
that referenced
this issue
Feb 1, 2020
Addresses: nodejs/community-committee#559 Guidance by: nodejs/community-committee#271 (comment)
keywordnew
added a commit
to keywordnew/mentorship
that referenced
this issue
Feb 1, 2020
Addresses: nodejs/community-committee#559 Guidance by: nodejs/community-committee#271 (comment)
There is a possible issue with the licence choice over at nodejs/mentorship#184 The guidance suggests:
The MIT license has specific mention of "software", which that repo does not have. Shall we switch to CC-BY-4.0? One could make the case that the material is, at least partly, documentation to be provided to users. |
@keywordnew I think that despite the "software" mention the suggestion was that for internal community documents it would still be ok. |
davidguttman
pushed a commit
to davidguttman/mentorship
that referenced
this issue
Feb 28, 2020
Addresses: nodejs/community-committee#559 Guidance by: nodejs/community-committee#271 (comment)
I've unarchived this repo so I can close all PRs and issues before re-archiving. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Quite a while ago #271 recieved the feedback we were waiting on. We should follow the feedback that was provided and ensure our repos are licensed correctly. We will need to audit the CommComm repos and figure out which are currently not licensed, and add the correct licenses to them.
I would also recommend submitting PRs and @ mentioning the appropriate teams to ensure that there are no objections - if there are, we will need to address them as necesssary.
The text was updated successfully, but these errors were encountered: