Leading an Open Source community at a large Enterprise - Jonas Rosland - Open Source Summit Japan 2017
•Download as PPTX, PDF•
0 likes•716 views
Creating an open source initiative at a large enterprise such as Dell EMC comes with both challenges and rewards. Making sure your community is engaged and your projects thrive takes time and effort. In this session, Jonas Rosland, Open Source Community Manager at {code} by Dell EMC shares experiences, failures, and gives a glimpse into how large enterprises can embrace and lead open source communities successfully.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Leading an Open Source community at a large Enterprise - Jonas Rosland - Open Source Summit Japan 2017
Similar to Leading an Open Source community at a large Enterprise - Jonas Rosland - Open Source Summit Japan 2017 (20)
Recently uploaded
Recently uploaded (20)
Leading an Open Source community at a large Enterprise - Jonas Rosland - Open Source Summit Japan 2017
- 1. Leading an Open Source Community at a large Enterprise Jonas Rosland Open Source Community Manager {code} by Dell EMC @jonasrosland
- 2. Open Source at Dell EMC – Contribute to Meaningful Open Source (OSS) projects – Develop and Support our Own Projects – Drive Awareness – Participate in relevant community projects – Act in the interest of building a community {code} by Dell EMC is a group of passionate open source engineers and advocates working to build a community through contribution, engagement and technical solution leadership. Platinum Sponsor
- 3. Open Source at EMC – The beginning
- 4. FIFI • Freedom • Innovation • Flexibility • Integration https://www.flickr.com/photos/garryknight/30412785095
- 9. A knotty puzzle may hold up a scientist for a century, when it may be that a colleague has the solution already and is not even aware of the puzzle that it might solve. - Isaac Asimov, The Robots of Dawn
- 10. Even proud and healthy individualism has its drawbacks. The greatest minds – working singly, even for centuries – cannot progress rapidly if they refuse to communicate their findings. - Same author, same book, same page
- 11. The {code} Community comes to life
- 13. We are a worldwide community
- 14. Picture from the community site codedellemc.com/community
- 16. Identify internal and external developers • Individuals who have created and published projects • Projects that augment Dell EMC products • Promote the individuals and their projects
- 17. DevHigh5 Promoting work by employees, partners and customers which augments Dell EMC products 97 projects have been shepherded through DevHigh5
- 18. Identify internal and external open source advocates • Individuals who are well known in the industry • They lead conversations around next-gen software- based infrastructure • They create content, blog, speak at conferences and more • Focused effort on promoting their work
- 19. The {code} Catalyst program An ecosystem of innovative open source advocates, developers and project managers across company boundaries
- 20. The {code} Catalyst program 26 individuals from 7 countries working at Docker, Red Hat, VMware, Intel, Sirius, Acquia, IBM, Codeship, Rancher, Mesosphere, BlockBridge, BT, Pivotal, Dell and Dell EMC
- 23. Community-driven projects • 97 projects have been shepherded through the DevHigh5 program since 2014 • The majority are still in ongoing development
- 24. Open source projects from the {code} team
- 25. The {code} Community contributes back
- 26. The {code} Community gives back
- 27. The {code} Community gives back
- 29. The community’s effect on business • Customer views of Dell EMC has changed • The community approaches us with new ideas, code and documentation • Community involvement with our projects leads to both customer and community success • New and interesting partners want to collaborate • Changed view of open source within Dell EMC
- 30. In summary, community building takes time • To grow a community you need to understand its members • Remove barriers – open and safe platforms for discussion • Encourage participation • Make contributing easy, interesting and rewarding • Connect on a personal level, both online and offline
- 32. #CodeOpen
Editor's Notes
- Add talking points to each point OSS projects: Docker, Mesos, Kubernetes, Cloud Foundry
- August 2014, we started a new initiative within then EMC entirely focused on open source with a goal of making EMC involved in open source in new and interesting ways
- Why would EMC be interested in participating in open source? We want to give our users the freedom of choice, the means of innovation, the flexibility to change things and the ability to integrate our products and projects easily into their existing environments.
- Since we wanted to lead the company into open source, we had to do some digging first to see what already existed
- We looked at how open source was being used within our company It was mostly using open source and not giving back to the community, which is fine for most businesses but we wanted to do more
- We also found several employees who were giving back to the open source community on both office hours and their own time. This is where it gets interesting.
- We wanted a way to communicate with employees and others in the open source space that we knew were interested in collaborating with us.
- That’s the reason we started our Slack team called the {code} Community. We wanted it to be an open place for discussions around anything open source, both within and outside the company. We made sure anyone could join in the conversation, and by opening it up we quickly saw an influx of employees, partners, customers and even competitors.
- In late 2015, an internal team at then EMC for a project called RackHD joined us, and brought with them a big influx in new members and messages. So much in fact that by early 2016 we saw that we reached 10,000 messages per week, essentially giving us a scrollback/backlog of just a week. This of course didn’t really work since we wanted to be able to point back to earlier discussions when questions arose about issues, projects, ideas etc. So after a brief period of negotiation we saw the need and benefit of paying for the great service Slack was giving us, and in return we got unlimited message retention and integrations. Yay! Since the beginning we’ve always been completely open, allowing anyone to join be it partners, customers or competitors.
- During our initial search for open source feelows within the company we found several already open sourced projects that were published on GitHub. We created an initiative called the DevHigh5 program, to promote work by employees, partners and customers which augments Dell EMC products. We set up guidelines for what a project should look like, with information about licensing, documentation, code quality and usability. This initiative proved to be a great way to reach out to people interested in open source and get them involved early on in our {code} Community.
- The {code} Catalyst program is focused on promoting thought leading members of the open source community by creating a candid dialogue between open source advocates, developers and project managers across company boundaries. Our goal is to create an ecosystem of innovative open source advocates who lead and advance emerging technology to support software-based infrastructures. According to Merriam-Webster, a catalyst is a substance that increases the rate of a reaction, spurring rapid change. With a catalyst, reactions occur faster because they require less activation energy and often only tiny amounts of the catalyst are needed. Based on this definition we see the {code} Catalysts as influential advocates of open source. They educate others on projects they are involved in, engage in conversations to advance software-based infrastructure and share real-life experiences with other members of the larger {code} Community.
- 14 people invited, 12 accepted, 2 have not responded 7 of the 12 are outside Dell EMC
- As a community we also see the value of our members getting to know each other on a personal level, which is why we started the {code} Assemblies: Get-togethers with industry veterans and newcomers, enjoying each others company and discussions ranging from containers to broken database schemas to finding love.
- AKA getting value out of the community