Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Your organization needs an OSPO, or be ready to fail!

Bitergia
October 04, 2019

Your organization needs an OSPO, or be ready to fail!

Talk abstract: Open source is becoming the main ingredient for companies to success. To achieve it, companies need to manage efficiently their relationship with open source projects. And that’s the main goal for companies’ Open Source Program Office (OSPO).

During this talk, you will learn about the benefits of having an OSPO in your organization, why should companies adapt to open source and adopt an OSPO, how it makes a difference to have a team responsible for viewing, managing, making critical decisions, contributions back to open source projects, and providing oversight for open source initiatives on their company and where they should start. Also, we will give real examples of how companies are doing this today and their impact for the community, like Samsung Open Source Group, Uber, and others.

Additionally, you will learn about communities and initiatives to help you having a successful OSPO, like TODO Group and CHAOSS, the importance of CHAOSS to give actual data and insights about open source projects and a bigger perspective with analytics dashboards, and how data and metrics from the OSPO can help companies tackle their corporate strategy.

Slides license: Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
https://creativecommons.org/licenses/by-sa/4.0/

Bitergia

October 04, 2019
Tweet

More Decks by Bitergia

Other Decks in Technology

Transcript

  1. Put you logo above this Your organization needs an OSPO,

    or be ready to fail! J. Manrique López de la Fuente CEO at Bitergia [email protected]
  2. Put you logo above this … and Open Source is

    eating the Software World “By 2022, over half of the code in 75% of new apps will be from external sources. The need to improve developer productivity is driving the use of open source and commercial code repositories”
  3. Put you logo above this Inbound and outbound open source

    software inbound Consume open source projects
  4. Put you logo above this Inbound and outbound open source

    software inbound outbound Consume open source projects Contribute to open source projects Release of new open source projects
  5. Put you logo above this OSPO role inbound outbound Consume

    open source projects Contribute to open source projects Release of new open source projects Open Source Program Office (OSPO)
  6. Put you logo above this Consuming OSS Licenses compliance Projects

    health Security flaws Talent attraction OSPO pain points tasks
  7. Put you logo above this Consuming OSS Licenses compliance Projects

    health Security flaws Talent attraction Contributing to OSS Leadership and footprint IP compliance Talent retention OSPO pain points tasks
  8. Put you logo above this Consuming OSS Licenses compliance Projects

    health Security flaws Talent attraction Contributing to OSS Leadership and footprint IP compliance Talent retention Releasing OSS Engagement Growth Leadership and footprint Talent attraction OSPO pain points tasks
  9. Put you logo above this Some Uber OSS metrics Repositories

    on GitHub 350+ Contributors worldwide 2,000+ Community projects: Jaeger, Horovod, Pyro, Apache Hudi, Kepler.gl 5 2 of the top open source projects on InfoWorld’s awards list 2 Stars on GitHub. Average 365 per repository 117K+ TODO Group member
  10. Put you logo above this Uber OSPO goals Collaboration (inbound

    & outbound) Attract talent Gain influence Give back Foster OSS participation
  11. Put you logo above this Why OSS development analytics? “Open

    sourcing a project is just as much a business decision as an engineering decision. We must be able to prove the value. Decisions should always be made based on facts - and facts are a product of metrics and analytics. The insights we can gain from metrics can make us better project maintainers.” Carsten Jacobsen (Open Source Developer Advocate, Uber)
  12. Put you logo above this How to measure OSS development?

    CHAOSS/GrimoireLab +30 data sources supported Predefined and customizable dashboards Contributors identity information management Rest API for data consumption 100% free, open source software GrimoireLab chaoss.github.io/grimoirelab Reporting Customization Analysis Strategy OSPO Analytics
  13. Put you logo above this Some examples How many and

    who are the core, regular and casual contributors?
  14. Put you logo above this Some examples How fast are

    projects dealing with external contributors/contributions?
  15. Put you logo above this 1. If you don’t have

    an OSPO in your organization, you should! 2. TODO Group has valuable resources to understand OSPO roles 3. CHAOSS helps you understand OSS development analytically 4. If you don’t have an OSPO yet… Seriously? AMA: [email protected] Recap