awesome-oss-monetization
Monetization strategies
A curated collection of monetization approaches for open-source software projects
🏆 A curated list of monetization approaches for open-source software. Feedback welcome!
765 stars
14 watching
21 forks
last commit: over 1 year ago
Linked from 1 awesome list
approachesawesomeawesome-listlibrariesmonetizationmonetizeopen-sourceoss
Awesome OSS Monetization v1.1 / Monetization Approaches / Unconditional Funding | |||
| Private Donations | |||
| Corporate Sponsoring | |||
| Funding Grants & Stipends | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Access | |||
| Paid Early Access | |||
| Paid Community Access | |||
| Advertisements on Website(s) | |||
| Paid Binary | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Content | |||
| Paid Online Courses | |||
| Paid Naming Rights | |||
| Paid Merchandise or Books | |||
| Paid Tools & Extensions | |||
| Paid Newsletter | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Licences | |||
| Paid Commercial Use / Dual-Licensing | |||
| Paid Premium Version / Open Core | |||
| Licensing the Brand | |||
| Sell White Label | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Services | |||
| Paid Hosting / Open SaaS | |||
| Paid Bundling / Widget Frosting | |||
| Paid Content Service | |||
| Paid Data Storage | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Use | |||
| Paid Usage | |||
| Kickback from Hoster | |||
| Paid Unlocking | |||
| Sell Telemetry | |||
| Blockchain-based distribution | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Paid Work | |||
| Paid Support | |||
| Paid Bugfixes / Bounties | |||
| Paid Feature Development | |||
| Paid Version Development / Crowdfunding | |||
| Paid Consultations | |||
| Paid Training & Certifications | |||
| Employment | |||
Awesome OSS Monetization v1.1 / Monetization Approaches / Special Monetization Approaches | |||
| Raise Venture Capital | |||
| Sell Project | |||
Awesome OSS Monetization v1.1 / Notes / Monetization Risks | |||
| CLA (Contributor License Agreement) | : If your project does not have a each contributor still holds the full rights to their contributed source code and could sue against a monetization. Github has a clause in their ToS which covers , but if you want to monetize you all should agree on the terms and sign a CLA or remove code from contributors unwilling to sign the new terms. Furthermore, a CLA protects the project if a contributor has copied (stolen) code from somone / somewhere else | ||
Awesome OSS Monetization v1.1 / Notes / Monetization Risks / CLA (Contributor License Agreement) | |||
| Contributor Agreement Chooser | To setup a CLA you can use the | ||
| CLA Assistant | To automatically prompt and collect "signatures" of your CLA for pull request you can use SAP's within GitHub | ||
Awesome OSS Monetization v1.1 / Notes / Monetization Risks | |||
| StackAid | in the collective can become a reason for dispute. If you want to monetize you should vote on how you want to distribute the income. The recipients of the money can be contributors but also bug bounties, conferences, or non-profits. A contract defining the distribution might be a good idea (Please ask a lawyer for help). Since recently there are services to distribute income for JavaScript packages such as , , or | ||
| fiscal host | : might be a bad idea - esp. if it is meant for the project. The money would have to be taxed twice - first by the individual and then by the final recipient. Furthermore, the taxation depends on the country / jurisdiction the recipients live in (or pay taxes in if they are Digital Natives). If you collect money for the project it might be a good idea to use a . As an individual it would be good to be registered as a Freelancer, to tax the income - but in some countries the normal income tax declaration might be sufficient (Please ask a tax advisor in your country) | ||
jnv/lists