Oscon 2013 - Lessons from building an open source community
Download as PPTX, PDF0 likes932 views
The document discusses how a company transitioned from closed source to open source software. It provides advice on building an open source community, including getting everyone in the company involved, building an ecosystem, making the software easy to consume, reducing bureaucracy for contributors, being transparent, and measuring community engagement. The company used tools like GitHub, Jekyll, and Jira to build their open source community site and track issues. Building a community takes hard work through an iterative process.
Oscon 2013 - Lessons from building an open source community
- 1. How We Built Our Community Uri Cohen Head of Product @ GigaSpaces @uri1803 #oscon 2013
- 2. How We Built Are 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
- 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 toolkit we used
- 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
- 20. Cut the Bureaucracy, Make It Easy for People to Contribute
- 21. Be Transparent
- 24. Our Toolkit
- 26. No Servers 26
- 27. For the Most Part, This Is What We Know 27
- 28. We Wanted Our Own L&F 28
- 30. Jekyll
- 31. Tracking
- 32. Search
- 34. Issue Tracking
- 35. Key Takeways • Building a community is HARD • It’s an iterative process • Have realistic expectations
- 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. Thank You!
Editor's Notes
- #14: It’s not just about the code, it’s about the way you run things 4 million projects on github, no one will know you’re there.
- #18: Support, devs, marketing, management Daily standups include community status Weekly meetings with marketing, events, blogs, discussions all the way up to CEO about goals, hurdles etc.
- #20: Use github, Readme, build, dependencies,changelog, State maturity, supported envs, license, docs, tags, announce, milestones…
- #21: Contributor agreement Pull request License
- #22: Share Your RoadmapShare Your Darkest Secrets
- #23: Measure everything you can – website, mailing lists, downloads, usage (downloads CDN, version checks)Always opt in, don’t be intrusive to the user
- #30: Github pages, github for code
- #31: What Jekyll does Who uses itGeared for Blog Sites Paging Categories TagsPluggable Supports several markups