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

Choose a license #45

Open
makrsmark opened this issue Feb 28, 2024 · 4 comments
Open

Choose a license #45

makrsmark opened this issue Feb 28, 2024 · 4 comments
Assignees

Comments

@makrsmark
Copy link
Collaborator

and then

  1. Update package.json
  2. Add License.md
  3. Add badge to README.md

References:

@kevinelliott
Copy link
Contributor

kevinelliott commented Feb 28, 2024

Yes!

Been holding back until we had more people contributing to have some thoughts around it.

Which do you (and this goes for anyone else that wants to comment) prefer and why?

@makrsmark
Copy link
Collaborator Author

makrsmark commented Feb 28, 2024

Definitely not my area of expertise, so I can be wrong in my understanding, I'd go with either

MIT - do whatever with it, just keep the license
GPLv3 - if you make changes, you have to open source it

Maybe helpful - https://opensource.org/licenses?categories=popular-strong-community

@makrsmark
Copy link
Collaborator Author

ISC - like MIT but simpler language - the default for npm packages

@makrsmark
Copy link
Collaborator Author

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

2 participants