1 / 37

Building an Open Source Community: Insights from Uri Cohen at OSCON 2013

In his OSCON 2013 talk, Uri Cohen, Head of Product at GigaSpaces, shares his company's transformative journey from a closed to an open source model. He outlines key strategies for fostering a thriving community, emphasizing that success is not just a developer's concern but a company-wide mindset. Key takeaways include the importance of involvement, transparency, and iterative growth in community building. Uri also discusses tools and practices that aided their transition, making it easier for users to contribute and engage.

chesmu
Download Presentation

Building an Open Source Community: Insights from Uri Cohen at OSCON 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How We Built Our Community Uri Cohen Head of Product @ GigaSpaces @uri1803 #oscon 2013

  2. How We BuiltAre Still Building Our Community Uri Cohen Head of Product @ GigaSpaces @uri1803 #oscon 2013

  3. What This Talk Won’t Cover

  4. How to Manage an Open Source Project

  5. When / What to Open Source https://www.madison.k12.wi.us/files/Calendar_0.jpg

  6. Which License to Choose

  7. And I won’t say “Software is eating the world” Really, I Promise…

  8. What I Will Talk about Our Journey as a company, moving from closed to open source • Do’s and Dont’s • The toolkitweused

  9. Some Background

  10. Why Open Source? Aside from the obvious reasons, it’s become a precondition

  11. So Here’s What You Shouldn’t Do

  12. This Developers, Developers, Developers, Developers, Developers, Developers

  13. Put It on Github and Think You’re Done http://octodex.github.com/hipster-partycat/

  14. Have a “Community Guy” that Handles All This OSS Stuff…

  15. Check the Mailing Lists Once a Week http://www.cetofnc.com/images/2009/angry_user.jpg

  16. What Worked for Us

  17. Get Everyone Involved It’s not a developer thing, it’s a company mindset

  18. Build Your Eco-System

  19. Make It Easy to Consume

  20. Cut the Bureaucracy, Make It Easy for People to Contribute

  21. Be Transparent

  22. Measure, Measure & Measure Some More

  23. Incentivize Users

  24. Our Toolkit

  25. Requirements…

  26. No Servers

  27. For the Most Part, This Is What We Know

  28. We Wanted Our Own L&F

  29. Github to the Rescue

  30. Jekyll

  31. Tracking

  32. Search

  33. User Forums &Feedback

  34. Issue Tracking

  35. Key Takeways • Building a community is HARD • It’s an iterative process • Have realistic expectations

  36. Resources • Community sitewww.cloudifysource.org • OSS project repo: github.com/CloudifySource/cloudify • Community web site repo:github.com/CloudifySource/cloudifysource.github.com • Jira: https://cloudifysource.atlassian.net/

  37. Thank You!

More Related