What R We Counting?
summary
GSK sets a deadline of end of 2025 and a target of 50% code in open-source languages, so the project extracts GitHub language stats via the GitHub API using the gh package, stores raw and transformed data in Azure Data Lake, schedules weekly runs with Posit Connect, and publishes Quarto and Shiny dashboards. Tracked metrics include relative R size, repo counts above a threshold, commits, PRs, merge conflicts and package mentions; built a GitHub Health alerting system and a tool catalog to answer adoption and ROI questions.
AI-written summary · about
chapters (15)
- 0:00Open source adoption challenges
- 1:25VP’s question like Apollo 13
- 2:54GSK’s R adoption journey
- 4:00Pharma regulations and GitHub
- 5:49GitHub APIs and gh package
- 7:36Overcoming analysis paralysis
- 9:03Automating metrics with Posit Connect
- 11:10Status updates to insights
- 12:16Proactive GitHub support
- 12:59Measuring tool usage and ROI
- 14:31From Houston to Mission Control
- 15:13Q&A on adoption goals
- 16:40Why resist open source tools
- 17:22Closed source pushback on adoption
- 18:28GitHub culture before R transition
related talks
42mMeasuring Ourselves GitHub’s Accessibility Scorecard
45mHow GitHub builds GitHub on GitHub
20mModernizing the Data Science Toolkit of a 40-year-old Market Research Company
45mHow GitHub builds GitHub with GitHub
17mProject Immortality: Using GitHub To Make Your Work Live Forever
45mOpening Keynote
45mHow Github uses GitHub to develop GitHub
10mKeynote: From “Open Source” to “Development in the Open”