Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Snowball Effect of Open Source

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.

181de1fb11dffe39774f3e2e23cda3b6?s=128

Armin Ronacher

June 14, 2022
Tweet

More Decks by Armin Ronacher

Other Decks in Technology

Transcript

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

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

  3. Armin's 
 Open Source 
 est. 2004

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

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

  6. The Open Source Lifestyle

  7. Direct and Open Communication Outcome Based Networking Con fl ict

    Resolution and Diplomacy International Community Building
  8. How Jinja met Sentry — how I met David

  9. 2004 The Journey Begins

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

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

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

  13. Jinja was born

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


    2007-03-26T17:51:52 <mitsuhiko> zeeg: me. but i don't count ;) 
 2007-03-26T17:56:38 <mitsuhiko> zeeg: if you have questions fell free to poke me :)
  15. Group Django Errors in a Database an itch to scratch:

  16. Sentry was born

  17. commit 3c2e87573d3bd16f61cf08fece0638cc47a4fc22 (HEAD) 
 Author: David Cramer 
 Date: Mon

    May 12 16:26:19 2008 +0000 
 
 initial working code
  18. independent projects, not much in common, but we kept crossing

    paths
  19. went to the same conferences

  20. used by the same communities

  21. similar licensing ideas

  22. endurance and perseverance

  23. adjusting to change

  24. I expected Jinja to die a long time ago

  25. Projects adjust to new environments

  26. JavaScript changed things

  27. Licensing Matters

  28. You can't force people to contribute back

  29. Do you want people to walk away?

  30. I want everybody 
 to use it

  31. A license is only as good as your enforcement

  32. Non Monetary Payo ff s

  33. got my fi rst job via Open Source

  34. I found international relationships via Open Source

  35. Sentry got its fi rst customers via Open Source

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

  37. Money Matters

  38. maybe you need a business model and revenue stream

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

    that call early
  40. services are easier to monetize, libraries need subsiziding

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

  42. Open Source in Companies

  43. some things take a lot of effort, and many folks

    need to do it
  44. There are benefits to collaboration, and very few risks to

    a business
  45. Take a bold step and Open Source internal tech and

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