Lessons Learned from Creating an OSPO at Goldman Sachs
summary
Goldman Sachs establishes an OSPO within nine months: feedback starts in November, strategy memo in April, founding team formed May–July and internal launch in August. The office tracks OKRs in Jira, documents a company inventory of contributors, enables BYOD contributions, runs a community newsletter and blog, and opens a Twitter account (gsdeveloper). Public projects include GS Quant, GS Collections (to Eclipse), and Legend (to FINOS). Legal collaborates closely and the initiative already joins OpenSSF and the TODO Group.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:22Agenda
- 0:58About Goldman Sachs
- 1:29Open Source
- 2:35Motivation
- 2:50Why an OSPO
- 3:57Planning
- 4:09Timeline
- 5:26The Planning
- 6:07Current State
- 6:35MultiYear Strategy
- 7:47Founding Team
- 8:33Open Source Champions
- 9:27Goals
- 10:38Structure
- 11:44Learnings
- 13:23Progress
- 15:04Questions
related talks
45mGoldman Sachs' Open Source Program Office - One Year In
42mBuilding the Open Source Program Office at Goldman Sachs
34mOpen Source at Goldman Sachs
31mLessons Learned After 1 Year Running an OSPO in Bancolombia (LATAM)
30mOSPOs in Finance: Ways to Overcome Industry Barriers to Accelerate OS Adap...
26mNavigating Open Source: Establishing an OSPO for Organizational Success
45mCulture Change: Building an OSPO in a Proprietary Software Company
01h 39mWorkshop: Building and Managing an Open Source Program Office