University-based Open Source Programs Offices
summary
A university OSPO faces messy reality not theory: Johns Hopkins has 24 academic calendars before COVID, $3 billion in research funding, and no consistent repo naming so the inventory is unknown; tools deployed include a GitHub Enterprise instance, a Sloan-funded false contributor fund, and work with Baturga to map projects. Built products include the Public Access Submission system—now PASS as Eclipse product—and BlueTests/Lutes integrations with the City of Paris and a West Baltimore center to help homeless find beds; these pilots run and reveal legal and governance friction points.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:48Carnegie Classification of Universities
- 4:29Funding Streams
- 10:19Semesters of Code
- 11:30Accreditation
- 15:29The Open Source License
- 18:04Best Practices from Corporate Hospitals
- 23:54What's the Potential for Inter-University of Collaboration
related talks
43mRise of the OSPO in Industry, Academia & Municipal Gov.
46mPanel Discussion: Lessons Learned: OSPOs in Universities
36mThe Evolution of OSPOs
26mOpen Source Program Offices
40mThree Cs to an Open Source Program Office
01h 02mThe Culture of Open Source between Institutions
38mBoF: Collaboration With Universities and Enterprises OSPO
26mNavigating Open Source: Establishing an OSPO for Organizational Success