Oss License Strategy

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

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.

Instructions onlyBusiness & Finance

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json41.6 KBapplication/json
references/business-model-licensing.md7.6 KBtext/markdown
references/contribution-policy.md7.1 KBtext/markdown
references/decision-record-example.md5.9 KBtext/markdown
references/license-families.md7.1 KBtext/markdown
references/published-findings.md17.1 KBtext/markdown
SKILL.md29.4 KBtext/markdown

Source and attribution

Source:samber/developer-relations-skillsinskills/oss-license-strategyat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal