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

License #316

Open
mahald opened this issue Oct 9, 2024 · 2 comments
Open

License #316

mahald opened this issue Oct 9, 2024 · 2 comments

Comments

@mahald
Copy link

mahald commented Oct 9, 2024

It's a promising project, but unfortunately it's using GPLv3, which can hinder business adoption.

@mahald mahald closed this as completed Oct 9, 2024
@AlexCheema
Copy link
Contributor

Hey @mahald what issues are there with this licence? Do you have a suggestion for another licence that would be better?

@AlexCheema AlexCheema reopened this Oct 9, 2024
@mahald
Copy link
Author

mahald commented Oct 9, 2024

GPL is often avoided by companies due to potential legal risks, including the obligation to share their own source code if their software is considered a "combined work" with GPL-licensed code, as explained here:

...

  • Do you want your project to be used as a dependency by other projects? Probably best to use the most popular license in your relevant community. For example, MIT is the most popular license for npm libraries.
  • Do you want your project to appeal to large businesses? A large business may be comforted by an express patent license from all contributors. In this case, the Apache 2.0 has you (and them) covered.
  • Do you want your project to appeal to contributors who do not want their contributions to be used in closed source software? GPLv3 or (if they also do not wish to contribute to closed source services) AGPLv3 will go over well.

...

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