-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring project up to open source community standards #507
Comments
Notes:
|
From awesome list PR template:
The license must be a Creative Commons license to be acceptable for the awesome list repo |
what sort of license should we use if it's people's data? |
Hmm. That's a very good point. Is there a way to protect the code with a license but leave the data.js file out? I don't really deal in licensing. |
This will be extremely complicated. Under the Berne convention, everything is copyrighted by default, which means that every person who has added themselves owns that snippet of code they've contributed. This means we will have to get permission from every single contributor to relicense their work under . My tip would be to have multiple licences for this project. The JS code of the website can be under MIT or ISC or whatever your favourite code licence is. You still need to get everyone's permission, but I guess it will be waaay fewer people. The README should be CC0-1.0, as it's the core of an Awesome list. |
I mainly noticed that there's no license in the repository.
I guess this one's probably for @wesbos. I'm personally more than happy for anybody to use this project as the base for theirs (fork, adapt & even use in a commercial setting).
Things GitHub Suggests (see Insights > Community):
The text was updated successfully, but these errors were encountered: