OSPOs in Academia: Increasing the Impact of Educational Ins...
summary
A remote-control instrumentation facility called CMU Cloud Lab is built to let anyone with campus credentials run materials and chemistry experiments, but only the code is nominally “open” without public repos or licenses so reproducibility fails because data, hardware protocols and AI pipelines remain closed. A campus research center secures $2.5M+ in industry and endowment funding to professionalize student projects; a two‑year Sloan grant creates a UC network across six campuses. The community now links into a 14-member Curious network and Helios ~100 members, and pilots include containerization and hiring community managers for sustainability.
AI-written summary · about
chapters (11)
- 0:00OSPOs in academia
- 1:23University OSPO challenges
- 3:51CMU Cloud Lab case study
- 7:42UC Santa Cruz OSPO journey
- 12:23Research-industry collaboration
- 16:38UCSC OSPO structure and impact
- 22:16UC OSPO expansion plans
- 24:23Global OSPO collaboration
- 28:16Helios leadership initiative
- 31:25OSPOs shaping research
- 34:19Q&A
related talks
26mUniversity-based Open Source Programs Offices
10mLightning Talk: Amplifying University Research Impact with Open Source
46mPanel Discussion: Lessons Learned: OSPOs in Universities
29mCollaboration with Universities and Enterprises OSPO: What's Next?
46mBoF: Collaboration with Universit...
38mBoF: Collaboration With Universities and Enterprises OSPO
23mOpen@RIT, Creation of a University OSPO and the First Year's Lessons Learned.
37mOpen-Source Science: Working with OSPOs to Accelerate Research in...