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 type suggestions #17

Open
kswartz26 opened this issue Jun 26, 2019 · 0 comments
Open

License type suggestions #17

kswartz26 opened this issue Jun 26, 2019 · 0 comments

Comments

@kswartz26
Copy link

kswartz26 commented Jun 26, 2019

Excellent tool and great article to go with it.

As someone who does open source license compliance for my company, I have a few suggestions on licenses to add/types to consider for them:

  • Add EPL 2.0 to weaklyProtective
  • Add CDDL 1.1 to weaklyProtective
  • Consider "CDDL / GPLv2 with Classpath Exception" as a single entry, which is the license previously used for many Java projects. (They are gradually moving to EPL v2.) The CPE is intended to move is more toward the weaklyProtective group, but in reality, it sort of sits between the two.
  • Add BSD+PATENTS to the weaklyProtective list. Hopefully this is quickly falling out of favor, but it is important to distinguish from regular BSD licenses due to its high risk and ineligibility for use with other major projects (like those run by Apache).
  • Add SSPL to the networkProtective list. This is the license used by MongoDB, and it is uber-protective.
  • Move WTFPL to publicDomain. Even though none of the licenses there are, strictly speaking, truly "public domain", these licenses all carry no obilgations for any type of use, and in that sense, WTFPL is the same.

Thanks, and keep up the good work spreading the gospel of licensing!

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

1 participant