Open Source Company Strategy

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

Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy.

Instructions onlyBusiness & Finance

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

PathSizeType
evals/evals.json45.9 KBapplication/json
references/boundary-tests.md13.7 KBtext/markdown
references/company-type-and-authority.md11.9 KBtext/markdown
references/operating-model.md6.7 KBtext/markdown
references/published-findings.md9.2 KBtext/markdown
references/strategic-motives.md7.5 KBtext/markdown
SKILL.md25.6 KBtext/markdown

Source and attribution

Source:samber/developer-relations-skillsinskills/open-source-company-strategyat commit98ed86d

License: MIT

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

Report or request removal