1 / 41

A Team Contributing Full-time to Open Source Projects

Learn how to successfully implement a dedicated in-house open source initiative in your company, even if it doesn't fit into the usual profiles. Discover how Musala Soft built a team of developers contributing full-time to open source projects, benefiting both the community and the company.

fbecky
Download Presentation

A Team Contributing Full-time to Open Source Projects

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. A Team Contributing Full-time to Open Source Projects A Primer on Making It Happen in Your Company EclipseCon Europe October 25th, 2017, Ludwigsburg

  2. Our Plan • Intro • Why discuss this? • Our Story • How to try this with your company? • Outro

  3. About Us IanchoDimitrov Dimitar Ivanov

  4. Why Discuss This? • Open Source is good – no need to explain why… • Dedicated in-house open source initiatives: • rare • …and especially rare in service companies

  5. The “Usual Suspects” Company Profiles • Business focused around open source products • Big ones open sourcing part of what they create • Heavily using or relying on open source products • Non-profit, focused on an open source product(s) • Academic projects publicly funded

  6. Why Discuss This? …so what if your company doesn’t fit in any of the “Usual Suspects” profiles?

  7. About You • Type of company you’re working for: • IT services? • IT products? • industry / non-IT? • Dedicated open source initiatives there? • yes – “usual suspects” profile? • yes – other? • no?

  8. Our Plan • Intro • Why discuss this? • Our Story • How to try this with your company? • Outro

  9. About Musala Soft What we are • Software development services since 2000 • 450+ experts in Bulgaria and Macedonia • Cloud Integration & API Mgmt., AI & Big Data Analytics, IoT, Smart Home, Industry 4.0 • Java, .NET, Front-end, Mobile, Data… • North America and EU (esp. Germany) • Telecom, Banking & Finance, Automotive, Public Sector

  10. About Musala Soft What we are NOT • We are not selling products / solutions • There is no single platform or tool we are significantly dependent on (be it open source or not) • We are not providing services around an open source platform / tool • We are not a big company …in short – we are also not one of the “Usual Suspects” for having dedicated open source development.

  11. Our Story The context • Smart Home & IoT • Qivicon / Telekom Smart Home • Musala Soft investing in people, hiring entry-level and less experienced developers The idea • Martin Momov

  12. Our Story Aligned with Strategic Priorities • Software development services since 2000 • 450+ experts in Bulgaria and Macedonia • Cloud Integration & API Mgmt., AI & Big Data Analytics, IoT, Smart Home, Industry 4.0 • Java, .NET, Front-end, Mobile, Data… • North America and EU (esp. Germany) • Telecom, Banking & Finance, Automotive, Public Sector …and in addition: • Big project with potential for scaling • Specific technology area (Java, OSGi) • Training new people: • not experienced (junior developers) • experienced but not in the area • Employer brand & image • Potential new business opportunities

  13. Our Story Convincing our Board of Directors to invest in the initiative • Aligned with our strategic direction – re: IoT, Smart Home, EU/Germany • An enabler for effective professional development of both experienced and less experience colleagues in our priority technology areas • We’ll add to our portfolio 1 more project in a focus area where we want to grow • We’ll start small – 2 people initially – mostly with less experienced colleagues • We want to give this a try – with a 6-month test phase – and we’ll monitor results regularly • It will help a lot with employer branding and positioning • It will be an enabler for new business – both for new clients and within existing ones

  14. How the Team Has Been Working • April, 2016– 1 Jr. Dev (full-time), 1 Sen. Dev (mentor, part-time) • focus on knowledge acquisition about Eclipse SmartHome and OpenHAB • work on “forgotten tasks” (waiting for years) – e.g. UI issues, annoying bugs that everybody just handled with workarounds

  15. How the Team Has Been Working • May, 2016 – 3 Jr. Devs (full-time), 1 Sen. Dev (mentor, part-time) • tutorials & documentation (OSGi) – incl. coding tasks and sample solutions • unit tests • development tasks “no one felt like doing” – e.g. migration to Jetty, 1-month work

  16. How the Team Has Been Working • Since June, 2016 until now – 4 Jr. Devs + 1 Mid-level Dev (full-time), 1 Senior Dev (mentor, part-time) • service integrations – e.g. RSS feed binding • device integrations – EnergenieMi|Home (smart plug, energy monitor…) • Static Code Analysis tool • expanding Unit Tests coverage • extending and keeping up-to-date Documentation and Tutorials • internal process – tracking issues, code reviews, pair programming

  17. The Team

  18. Win-Win-Win? So – is it really a win-win-win? …for: • the Community & the Project • the Team • the Company

  19. The Community & Project – Sample Contributions

  20. The Community & Project – Sample Contributions

  21. The Community & Project – Sample Contributions

  22. The Community & Project – Sample Contributions Static Code Analysis Tool • The problem: • Redundant developers’ mistakes in the new PRs • Slowing down the contribution process • The solution: • Static code analysis – findbugs, checkstyle, pmd • Custom checks for the coding guidelines • So far – 26 custom checks and growing

  23. The Community & Project – Sample Contributions

  24. The Community & Project – Summary of Contributions • 100+ merged PRs for the Static Analysis Tool • 16 merged PRs in openHAB Docs • 75 merged PRs in openHABAddons • 70 merged PRs in Eclipse SmartHome • 15+ bugs found & reported

  25. The Community & Project – Sample Feedback

  26. The Community & Project – Sample Feedback

  27. Win-Win-Win? So – is it really a win-win-win? …for: • the Community & the Project • the Team • the Company

  28. The Team (and Alumni) Svilen Lyubomir Tanya Kristina Velin Dimitar Alumni: Erdoan Mihaela Alexander Petar Elena Kiril Miroslav

  29. The Team – How Do They Feel? Q: How do you feel about being part of the Open Source Team? The Open Source team was the best place for an embarrassed junior like me. I was coming to the office really motivated each day! Amazing experience and big chance for me to grow as a programmer Very interesting, dynamic, competitive, hard and inspiring! My code was reviewed by professionals from all over the world and I learned a lot from them.

  30. The Team – How Do They Feel? Q: The most useful skills you've gained in the Open Source Team? I've learned to write clean and high quality code. I've learned to face the big projects without fear. I've learned to cut the complex tasks into solvable pieces. I've learned to test my code. I've broadened the scope of my skills a lot by learning new concepts and technologies.

  31. The Team – How Do They Feel? Q: What was the most exciting part of you working in the project? The most amazing thing was to touch some real devices and integrated them into an open source project! I appreciate the most that I became part of the huge openHABcommunity. I had the chance to meet a lot of new people and to learn a lot!

  32. Win-Win-Win? So – is it really a win-win-win? …for: • the Community & the Project • the Team • the Company

  33. The Company What are the results so far? • Professional development of people • full success – proven quick growth in terms of technology skills, professional attitude to quality, process, communication skills, distributed team work, etc. • Employer brand and image • extended external exposure via conferences and events • the initiative is very much appreciated internally • highly motivated team members

  34. The Company What are the results so far? • Business (opportunities) • 2 direct project opportunities, 1 contracted • 3 indirect project opportunities, 1 confirmed and 1 still in discussions • Great appreciation for the initiative by existing customers • Broadened expertise and experts pool in the strategic area (IoT, Smart Home) • Extended exposure, business development and networking opportunities

  35. Win-Win-Win? So – is it really a win-win-win? …for: • the Community & the Project • the Team • the Company

  36. Our Plan • Intro • Why discuss this? • Our Story • How to try this with your company? • Outro

  37. How to try this with your company? Strategy • Put yourself in the shoes of the company management • Come up with an Open Source initiative that makes sense in the long-term for the company • Make sure the initiative is aligned with as many as possible from the strategic company goals • Try to align the initiative with the goals of HR/Talent Development, Sales, Ops/Delivery and PR • Start small (and as inexpensive as possible) • Don’t even start “officially” – aim for a test / trial initiative – for 6 months for example • Measure, report and discuss progress regularly, strictly and transparently • Regard the initiative as long-term from day one – and treat it as such

  38. How to try this with your company? Plan – Preparation & Convincing the Management to Invest • Do your analysis based on the strategic points – and come up with a rough initial idea • Research and find 2-3 Open Source Projects – that would be good candidates • Talk to HR/Talent Development, Sales, Ops/Delivery and PR – get their feedback and advice • Follow-up on feedback, do additional research, and come up with 1 or 2 specific ideas. Describe them – in short but clearly – addressing all points related to alignment with strategic goals, expected direct and indirect benefits in different areas – and do not exaggerate! • Create an initial plan for kicking-off a test phase • Approach Top Management – present the idea and request their opinion and advice

  39. How to try this with your company? Plan – During • Provide progress updates from the beginning • Research and find 2-3 Open Source Projects – that would be good candidates

  40. : ) Thank you for your attention! Dimitar.Ivanov@musala.com https://www.linkedin.com/in/dstivanov Iancho.Dimitrov@musala.com https://www.linkedin.com/in/iancho …and let’s keep in touch:

  41. - 1 0 + 1 Evaluate the Sessions Sign in and vote at eclipsecon.org

More Related