You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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:
Thanks, and keep up the good work spreading the gospel of licensing!
The text was updated successfully, but these errors were encountered: