This document discusses strategies for making free and open source software profitable, including:
- Earning money through customization services, support contracts, documentation/training, and paid plugins/versions while the core software remains free.
- Gaining funding from organizations, donations, ads, university partnerships, and corporate customers interested in the software.
- Releasing often with detailed changelogs and high quality documentation to build a user base and gain feedback to improve the software.
8. Free Software is cool but where is my money? ... profit? ... I need food to live! ... not sustainable
9. Rewards for Players For Companies Low-cost goodies Market evaluation and campains Easy of training and incentives for schools Creation of standards Easy to widespread and grow its use Motivational skills for the best developers Modularization culture Quality assessment Competition annihilation
10. Rewards for Players For Developers Hobby and fun Networking for hackers Curriculum improvement Responsibility assessment Knowledge of the whole development cycle Leadership development and evaluation Community knowledge for hiring Talks :)
11. Open Source is cool and it helps you to make money ... it is profitable ... it is fun ... it is sustainable
12. Open Source vs Free Software Open does not mean freedom Focus on Business Focus on People
16. Capture an Idea Use linux to know how people work Homeworks/Your Needs Crazyness/absurds Keep it simple, fast and VERY small It’s OK to copy You don’t like something? Create it again Forget about competitors Fork and Improve
19. How to Compute Ideas NETRA CATRA Marketing, Sports Games, Movies Medicine Display 3D Display 1D? Sound 3D Smell 3D Touch 3D Displays 4D? Multi-focal Displays Holograms Projector-based 3D Wave Optics Ray Optics Glasses-Free Context-Aware User-Sensible
25. Prove it: Demo or DIE An idea alone is worthless Everybody has good ideas Implementation matters! Interface matters Social network matters Spreading matters Easy live demos, videos, screencasts, blogs, twitter Code snippets, documentation, tutorials Business pitches, fund raising, foundation grants
27. Project Check-list Project page Documentation / User Manual Installation Notes License Repository / Version control SourceForge GitHub Feedback Page Wiki Discussion Group / Forum News Channel Blog - Best Twitter
28. Project Page Anatomy Goals Future of the project? What expect from it? Features and flaws Be sincere TO-DO List & Contribution Keep always updated Download Documentation Installation Notes Use Uninstall Snapshots and Screencasts
29. Quality-Based Software Make sure you are doing the best Minimum bugs, beautiful code Test driven development helps a LOT Unit test, Unit test, Unit test!! Feel free to release many beta versions Make nice videos and screencasts Believe me, you need them
30. Releasing and Feedback On releasing a version: Binary code and instructions Source code and instructions Detailed change-log and high-level news item Make packaging: .deb, .rpm and .yum Ask friends to test the software and instructions Be kind People will make critics. Don’t go ofensive. Good documentation and fast feedback action
31. Language and Internacionalization Source code: Always in english. Translate everything! Webpage: Start in portuguese. Make a first draft for an engligh website Other people can review it. Learn how to i18n of your environment Translation is the MAIN source of collaboration
32. Open Source Funding Saving time and money ONGs are usually awesome Allow donation Vakinha, Paypal, and others Adsense University partnerships They can provide servers and infrastructure Search for incubators Focus on corporate market. Who can get a lot of money from your software?
33. Open Source-based Company Your own company Customization services and support Documentation and training Warranty Plugins or paid improved version Award the best commiters Talks, talks and talks Pay for the best commiters go present Reward plan and gifts
34. Project Discontinued Projects die. Accept that. Let other people continue your work Keep the code on-line People can fork it Or learn from your mistakes Publish! People are relying on you, they need to know