Skip to content
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

Open
HugoDF opened this issue Jan 21, 2020 · 5 comments
Open

Bring project up to open source community standards #507

HugoDF opened this issue Jan 21, 2020 · 5 comments

Comments

@HugoDF
Copy link
Collaborator

HugoDF commented Jan 21, 2020

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):

  • Code of conduct
  • Contributing guidelines (although I guess we have part of that in the README)
  • License
  • Issue templates
@iamandrewluca
Copy link
Collaborator

Notes:

@transiient
Copy link
Collaborator

From awesome list PR template:

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.
    Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).
A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.

The license must be a Creative Commons license to be acceptable for the awesome list repo

@wesbos
Copy link
Owner

wesbos commented Jan 27, 2020

what sort of license should we use if it's people's data?

@transiient
Copy link
Collaborator

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.

@kytta
Copy link
Contributor

kytta commented Jan 7, 2023

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. src/data.js will stay non-free, I guess 🤷‍♂️

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

No branches or pull requests

5 participants