Bring project up to open source community standards

wesbos / awesome-uses

A list of /uses pages detailing developer setups, gear, software and configs.

https://uses.tech

4.58k stars 1.4k forks source link

Bring project up to open source community standards #507

Open HugoDF opened 4 years ago

HugoDF commented 4 years ago

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 commented 4 years ago

Notes:

Good example of community guidelines https://github.com/mdx-js/.github

transiient commented 4 years ago

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 commented 4 years ago

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

transiient commented 4 years ago

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 commented 1 year ago

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 🤷‍♂️