Intelligent Open Source - Daniel Izquierdo, Bitergia & Jim Jagielski, Uber

Uber has been contributing and producing open source since its inception. During the last years, it has started its own Open Source Program Office with the aim of better contributing to the open source world and becoming a good open source citizen.

However, what makes a good open source citizen and how do we interpret the health of our open source activities? These are the questions that Uber and Bitergia have tried to answer together through the analysis of the several aspects of the Uber open source ecosystem.

By this ecosystem, this means Uber developers working in third party open source projects, and at the same time, external developers contributing to currently lead or previously donated open source projects.

For this, four main areas of analysis have been identified as key for the health of Uber open source activities:
1- Engagement: as in Uber developers engaged in third party open source projects, and as in external open source developers engaged in Uber projects.
2- Collaboration with other organizations in the open source ecosystem.
3- Health of projects that matter to Uber
4- Software development performance, and recognition and celebration of contributions

Transcript

1. Intelligent Open Source Daniel Izquierdo, Bitergia Jim Jagielski, Uber #ossummit @dizquierdo @jimjag
3. “Uber is committed to enabling collaboration for everyone, everywhere through open source.” https://uber.github.io
4. But, what does it really mean?
5. Engagement Collaboration Health Performance & Recognition
6. Engagement External contributions of Uber developers in third party open source projects
7. OSS Ecosystem Uber OSS Ecosystem Uber Developer
8. OSS Ecosystem Uber OSS Ecosystem Uber Developer Non Uber Developer X OSS Ecosystem
9. OSS Ecosystem Uber OSS Ecosystem Uber Developer Non Uber Developer X OSS Ecosystem
10. OSS Ecosystem Uber OSS Ecosystem Uber Developer Non Uber Developer X OSS Ecosystem
11. OSS Ecosystem Uber OSS Ecosystem Uber Developer Non Uber Developer X OSS Ecosystem
12. Engagement - Questions Uber developers engaged in third party OSS Projects External OSS developers engaged in Uber projects
13. ====> Issues Opened ====> PRs Opened Personal and Uber projects are ignored <= Size = Nº Contributors
14. ====> Issues Opened ====> PRs Opened Note - Personal and Uber projects are ignored Timeframe - Last 2 years of analysis <= Size = Nº Contributors Pyro-ppl cockroachdb Apache facebook
15. Pyro-ppl Cockroachdb PRs Opened Blue dots are developers Pink dots are GitHub Orgs (not Uber related) Edge = a developer opened a PR in that GitHub Org
16. PRs Opened, last couple of years, by Uber and non-Uber employees participating at any GitHub Organization, but Uber ones
17. Collaboration Working together with other organizations in the open source ecosystem
18. 2013 Q3&Q4 VS 2020 Q1&Q2 Each dot is a developer Each color is an organization/company
19. Health Focused on understanding evolution, deltas, and KPIs over time for activity and community
20. Activity - Last Active Repositories by Data Source
21. Activity Repos Lifecycle Activity Active Repositories over time
22. Community - Active Contributors Over Time COVID-19?
23. Performance & Recognition Processes Improvement & Celebration of contributions
24. Performance - Review Efficiency Index (PRs closed / New PRs) COVID-19?
25. Performance - PR Lead Time - Time to close COVID-19?
27. If you want to learn a bit more Uber Open Source Program - TODO Group https://todogroup.org/blog/why-we-run-an-open-source-program-uber/ GrimoireLab - CHAOSS project https://chaoss.community Bitergia Analytics https://bitergia.com/ospo/