OSPO Data Pyramid
summary
Red Hat OSPO builds Project Aspen with a Python data stack (Dash/Plotly, pandas) and an Augur-backed relational DB to give direct, prejoined contributor-level data; the front end 8Knot plus Repel research notebooks produce visualizations like contributor engagement, PR staleness, bus/lottery factor and project velocity. Materialized views on Postgres make slow queries live, cutting what once took 10–40 hours to about 20 minutes and feeding cross-org reports that support C-suite alignment.
AI-written summary · about
chapters (14)
- 0:00OSPO Data Pyramid intro
- 0:43Red Hat data history
- 3:58Project Chaos & Augur
- 6:06San Diego to Aspen
- 7:12Project Aspen overview
- 9:42Aspen for OSPO decisions
- 11:53OSPO Data Pyramid concept
- 12:57Pyramid base communities
- 15:24Community health visuals
- 19:19Cross-organization collaboration
- 21:05Internal reports & feedback
- 23:30Company & OSPO alignment
- 25:17Closing & future goals
- 26:23Q&A on Augur & visuals
related talks
25mData Science for OSPO: OSS Trends Found from Developer Activities
39mSPRUCE it up! Open Source GreenOps at scale
44mUSER-FACING, REALTIME ANALYTICS USING APACHE PINOT
38mBI DataOps Development Process
43mFrom Data Tsunami to Actionable Insights
27mStream, Store, Visualize: Fast-Track Real-Time Analytics the OSS Way
36mOpenbytes Builds Open Dataset Standards and Schema Aiming to Bring Transformational Changes to AI by Making Open Datasets More Available and Accessible
29mOpen Source Powers The Modern Data Stack