oss-sponsors-brand-strategy

Builds a corporate open-source sponsorship portfolio covering mandate, budget, targets, procurement, and measurement.

2|Updated Sep 6, 2026
One-click install
npx skills add https://github.com/samber/developer-relations-skills --skill oss-sponsors-brand-strategy-samber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-sponsors-brand-strategy
Source: https://github.com/samber/developer-relations-skills/tree/main/skills/oss-sponsors-brand-strategy
Command: npx skills add https://github.com/samber/developer-relations-skills --skill oss-sponsors-brand-strategy-samber

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Companies that want to fund open source often have no defensible way to decide which projects and maintainers to sponsor, how much to pay each, or how to prove the money worked. This Skill turns a vague intention to give back into a complete, auditable sponsorship portfolio. ## Core Features & Use Cases - Mandate and allocation design: Picks a primary mandate (supply-chain assurance, reach, internal engagement, or public values) and ranks the four allocation models - breadth across dependencies, depth on key projects, foundation membership, and an employee-nominated FOSS fund. - Target discovery and scoring: Resolves the dependency graph from a lockfile or SBOM, verifies funding destinations, and scores candidates on exposure, fragility, audience fit, and relationship value. - Procurement, policy, and measurement: Covers invoiced billing minimums and fiscal hosts, publishes a policy on what sponsorship does not buy, and defines per-mandate metrics with renewal thresholds. - Use Case: A VP of Engineering with $80k asks where it should go; the Skill interviews for mandate and constraints, then produces a portfolio brief with budget split, ranked targets, payment path, and a measurement plan. ## Quick Start Ask the Skill to design an open-source sponsorship portfolio for your company given your budget, headcount, and primary goal.

Frequently Asked Questions about oss-sponsors-brand-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which open source projects my company should sponsor?

Start by naming one primary mandate - supply-chain assurance, reach, internal engagement, or a public values commitment - then resolve your dependency graph from a lockfile or SBOM and score candidates on exposure, fragility, audience fit, and relationship value.

How much should a company budget for open source sponsorship?

A published industry pledge asks for more than $2,000 per full-time-equivalent developer per year as a floor, while one company that disclosed actual spend reported $3,700 per developer. Both figures drift, so re-check them before quoting.

What is a FOSS Contributor Fund and how do I run one?

A FOSS Contributor Fund pays a fixed amount per cycle to one project nominated and voted on internally, documented by O'Brien and Grover. Nominations are open to everyone, but only employees who contributed to open source during the cycle may vote.

Can sponsorship money count if it goes to our own employees or projects?

No. Pledge-style programs exclude payments to company-controlled projects, software benefiting only the payer, maintainers the company already employs, and arrangements returning substantial benefits beyond minimal acknowledgment.

What happens when switching GitHub Sponsors to invoiced billing?

Switching an organization to invoiced billing cancels all existing sponsorships, and maintainers receive a cancellation email. Invoiced billing carries a $5,000 minimum per invoice, 30-day terms, a 3% service fee, and a 3-year agreement.

How do you measure the return on sponsoring open source maintainers?

Measure per mandate rather than with last-click attribution: coverage of fundable dependencies for supply chain, verified placements and referral traffic for reach, and employees contributing per cycle for engagement. Publish an annual report with totals per recipient.