par Jérémie Fays, 13 novembre 2013

1. Become rich & famous
thanks to
open source
Jérémie Fays
TTO University of Liège (Be)

2. There’s more to OS than this!

3. Why develop in OS ?

4. Why develop in OS ?
Become famous

5. Why develop in OS ?
Become rich
Become famous

6. Freedom to operate

7. Why NOT develop in OS ?
Become rich
Become famous

8. Plan
1. Become famous
2. Become rich

9. 1. Become famous

10. 1. Become famous
"
"
"
"
Open Source is trendy
There are little kingdoms
That could bring you research contracts
You could pass on TV

11. 1. Become famous
" Bad code smells badly
" Only little control on success
" It’s easier to become a pop star

12. Users community
"
"
"
"
"
Feedback / bug detection
Contribute to user guide
Translate user guide
Translate software
Users marketing
è All those people depend on me !

13. Users community
"
"
"
"
Attract users (marketing)
Answer questions/feature requests
Documentation
Roadmap

14. Developers community
"
"
"
"
Bug fixes
New features
New competencies
‘Core’ developers
è I’m not alone anymore !

15. Developers community
"
"
"
"
"
"
Setup collaboration tools
Developer guidelines
Modular architecture
Manage commit rights
Code quality/reviewing
Loss of control / Risk of fork

16. Success makes your soft…
§ Grow faster
§ Become pro
But requires serious commitment !

17. 2. Become rich
Let’s talk business !

18. Business risks
"
"
"
"
No license fees
Service competitors on your software
Software competitors could copy
Fork risk

19. Business opportunities
"
"
"
"
Open Source is mandatory (public sector)
Users marketing
Volunteer coders
Customer added value :
" Try before you buy
" Avoid lock-in
" Quality audit

20. Business models

21. Alternative
§ Sponsoring
§ Download subscription
§ Donation

22. Services
Training, audit, consulting
Tailored development
Authorized partners

23. Authorized partners : TAO
Revenue stream
– Tailored developments
– Royalties from authorized partners
What do partners gain ?
– Use of known trademark value
– Bring leads & bidding support
– Support level 3
– Training
– Support for the 3 first leads

24. Dual licensing
§ Proprietary compatible
§ Enhanced pro version

25. Added Value products
§ Documentation
§ Additional software
§ Hardware

26. « Customer pooling »
§ Propose specifications
§ Pool customers to share costs

27. Spin-offs...
Revenues for the lab?
§ Transfer proprietary à dual-license
§ Authorized partners
§ Research collaborations

28. Summary
§ Becoming famous requires commitment
§ Becoming rich requires a value proposition

29. Advertisement
§ The researcher’s guide – Creating software at
Ulg
§ http://www.interface.ulg.ac.be/valorisation/princA.php
§ (available since June 2012)
§ The “Anonymous Geeks”
§ monthly meetings since May 2013
§ Métriques et critères d’évaluation de la
qualité du code source d’un logiciel
§ Coming soon
§ A guide on Open Source Business Models
§ Who want to contribute ?

30. We are here to help…
..and to learn !
Jérémie Fays
j.fays@ulg.ac.be
+32 4 349 85 21
www.linkedin.com/in/jeremiefays

31. …and to eat.
It’s lunch time !
Jérémie Fays
j.fays@ulg.ac.be
+32 4 349 85 21
www.linkedin.com/in/jeremiefays