The Snowball Effect of Open Source

When contributing to Open Source projects, do you ever wonder how to get it more attention or even move it from a side project into something that is commercially available? In this session, you’ll hear about the intertwined story of two Open Source projects — Sentry and the Jinja Template engine — and how these open source projects got snowballed into the commercial world. IP rights, Business Source Licenses, challenges, lessons that can be learned looking back at more than 18 years of Open Source software development - you’ll hear it all. Added bonus is learning how to sustain a culture of support and contribution to Open Source within your own organizations.

Transcript

1. The Snowball
   E
   ff
   ect of
   Open Source
   Armin @mitsuhiko Ronacher
   Sentry
   

   View Slide

2. Hi I’m Armin
   and I Love
   and Live
   Open Source
   
   
   

   View Slide

3. Armin's
   

   Open Source
   

   est. 2004
   

   View Slide

4. Flask, Werkzeug,
   Jinja, Twig,
   Pygments, Sphinx,
   Insta, Sentry, …
   

   View Slide

5. Flask, Werkzeug,
   Jinja, Twig,
   Pygments, Sphinx,
   Insta, Sentry, …
   

   View Slide

6. The Open Source
   Lifestyle
   

   View Slide

7. Direct and Open
   Communication
   Outcome Based Networking
   Con
   fl
   ict Resolution and
   Diplomacy
   International Community
   Building
   

   View Slide

8. How Jinja met
   Sentry — how I
   met David
   

   View Slide

9. 2004
   The Journey
   Begins
   

   View Slide

10. “Microsoft is
    
    
    bad, let's use
    
    
    Linux”
    

    View Slide

11. hacked around on
    phpBB for Ubuntu,
    wanted to port it to
    Python
    

    View Slide

12. Python didn't have
    the right tools
    an itch to scratch:
    

    View Slide

13. Jinja was born
    

    View Slide

14. 2007-03-26T17:48:20 have any of you looked into jinja?
    

    2007-03-26T17:51:52 zeeg: me. but i don't count ;)
    

    2007-03-26T17:56:38 zeeg: if you have questions fell free to poke me :)
    

    View Slide

15. Group Django Errors
    in a Database
    an itch to scratch:
    

    View Slide

16. Sentry was born
    

    View Slide

17. commit 3c2e87573d3bd16f61cf08fece0638cc47a4fc22 (HEAD)
    

    Author: David Cramer
    

    Date: Mon May 12 16:26:19 2008 +0000
    

    

    initial working code
    

    View Slide

18. independent
    projects, not
    much in common,
    but we kept
    crossing paths
    

    View Slide

19. went to the same
    conferences
    

    View Slide

20. used by the same
    communities
    

    View Slide

21. similar licensing
    ideas
    

    View Slide

22. endurance and
    perseverance
    

    View Slide

23. adjusting to
    change
    

    View Slide

24. I expected Jinja to
    die a long time ago
    

    View Slide

25. Projects adjust to
    new environments
    

    View Slide

26. JavaScript changed
    things
    

    View Slide

27. Licensing
    Matters
    

    View Slide

28. You can't force people to
    contribute back
    

    View Slide

29. Do you want people to
    walk away?
    

    View Slide

30. I want everybody
    

    to use it
    

    View Slide

31. A license is only as good
    as your enforcement
    

    View Slide

32. Non Monetary
    Payo
    ff
    s
    

    View Slide

33. got my
    fi
    rst job
    via Open Source
    

    View Slide

34. I found
    international
    relationships via
    Open Source
    

    View Slide

35. Sentry got its
    fi
    rst customers
    via Open Source
    

    View Slide

36. Sentry bene
    fi
    ts
    and shares
    contributions to
    core technologies
    

    View Slide

37. Money Matters
    

    View Slide

38. maybe you need a
    business model and
    revenue stream
    

    View Slide

39. not every Open Source
    project must make money,
    but make that call early
    

    View Slide

40. services are easier to
    monetize, libraries need
    subsiziding
    

    View Slide

41. consider license
    restrictions to stay true to
    your goals.
    

    View Slide

42. Open Source in
    Companies
    

    View Slide

43. some things take a lot of
    effort, and many folks
    need to do it
    

    View Slide

44. There are benefits to
    collaboration, and very
    few risks to a business
    

    View Slide

45. Take a bold step and
    Open Source internal tech
    and start collaborating
    

    View Slide

46. Want to talk /
    questions?
    
    
    twitter.com/@mitsuhiko
    

    View Slide