Forming Lasting Relationships Between OSPOs and Legal Departments.
summary
Explains concrete steps to shift legal from “risk” to “asset” by building cross‑functional bodies, a documented approval flow and tooling: license scanning that gates product intake, a contribution intake form with a two‑week approval SLA, and a centralized project map of 200 projects to track approvals. Recommends creating a mandated license review board with legal required to sign off, and using the OpenChain spec as an external standard to justify legal investment and consistent decisions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:08IETF
- 2:10Open Source Awareness
- 3:56Whats Your Job
- 5:17How Do You Form Relationships
- 11:42The History of Bad Practices
- 14:16How to Lift Your Legal Departments
- 18:27Division of Responsibilities
- 20:17Open Source Projects
related talks
19mHow To Talk To Your Lawyer About Open Source
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
15mShifting Open Source Compliance Activities Left
26mNavigating Open Source: Establishing an OSPO for Organizational Success
01h 39mWorkshop: Building and Managing an Open Source Program Office
40mThree Cs to an Open Source Program Office
30mDemystifying OSPOs
26mOpen Source Program Offices