Legal & Compliance
Oss LICENSE Strategy
Chooses an open-source project's license and contribution policy as one decision - permissive vs weak, strong or network copyleft, dependency-driven compatibility constraints, DCO vs CLA vs nothing, dual licensing and open core, source-available options (BUSL, FSL, Elastic License, SSPL), and the fork risk of relicensing. Use whenever someone asks which license to pick, whether MIT, Apache-2.0, GPL or AGPL fits, whether to require a CLA or a DCO sign-off, how to relicense an existing project, whether AGPL really protects against cloud providers, or which LICENSE, SPDX and NOTICE files to ship - even if they only voice a legal worry. Not what the company open-sources at all - use samber/developer-relations-skills@open-source-company-strategy. Never legal advice.
- Publisher / source
- samber/developer-relations-skills (found on skills.sh)
- Upstream record
- samber/developer-relations-skills
- Version
- Version 3
- Published
- Publication review
- Approved for publication
- Content fingerprint
03bf7e008a13b9b7cb6b72d3716f17749470cd3ef40d253113f5421712339464