Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Oscon 2013 - Lessons from building an open source community

Related Books

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

  • Be the first to like this

Oscon 2013 - Lessons from building an open source community

  1. 1. How We Built Our Community Uri Cohen Head of Product @ GigaSpaces @uri1803 #oscon 2013
  2. 2. How We Built Are Still Building Our Community Uri Cohen Head of Product @ GigaSpaces @uri1803 #oscon 2013
  3. 3. What This Talk Won’t Cover
  4. 4. How to Manage an Open Source Project
  5. 5. When / What to Open Source https://www.madison.k12.wi.us/files/Calendar_0.jpg
  6. 6. Which License to Choose
  7. 7. And I won’t say “Software is eating the world” Really, I Promise…
  8. 8. What I Will Talk about Our Journey as a company, moving from closed to open source –Do’s and Dont’s –The toolkit we used
  9. 9. Some Background
  10. 10. Why Open Source? Aside from the obvious reasons, it’s become a precondition
  11. 11. So Here’s What You Shouldn’t Do
  12. 12. This Developers, Developers, Developers, Developers, Developers, Developers
  13. 13. Put It on Github and Think You’re Done http://octodex.github.com/hipster-partycat/
  14. 14. Have a “Community Guy” that Handles All This OSS Stuff…
  15. 15. Check the Mailing Lists Once a Week http://www.cetofnc.com/images/2009/angry_user.jpg
  16. 16. What Worked for Us
  17. 17. Get Everyone Involved It’s not a developer thing, it’s a company mindset
  18. 18. Build Your Eco-System
  19. 19. Make It Easy to Consume
  20. 20. Cut the Bureaucracy, Make It Easy for People to Contribute
  21. 21. Be Transparent
  22. 22. Measure, Measure & Measure Some More
  23. 23. Incentivize Users
  24. 24. Our Toolkit
  25. 25. Requirements… Code Docs Issues Analytics SEO Search Forums IRC Videos Blogs Comments Social 25
  26. 26. No Servers 26
  27. 27. For the Most Part, This Is What We Know 27
  28. 28. We Wanted Our Own L&F 28
  29. 29. Github to the Rescue
  30. 30. Jekyll
  31. 31. Tracking
  32. 32. Search
  33. 33. User Forums & Feedback
  34. 34. Issue Tracking
  35. 35. Key Takeways • Building a community is HARD • It’s an iterative process • Have realistic expectations
  36. 36. Resources • Community site www.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. 37. Thank You!

×