Oss License Strategy

samber/developer-relations-skills/skills/oss-license-strategy

作者 samber98ed86da8babMIT2 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫10 天前更新

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.

僅含說明Business & Finance
  1. 98ed86da8bab目前提交 98ed86d發布於 2026年10月8日

來源與署名

來源:samber/developer-relations-skills位於skills/oss-license-strategy提交98ed86d

授權條款: MIT

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架