~/talk

How Future-Proof Is Your OSPO? Avoid These 5 Common Missteps for Better Outcomes

links:none on file
slides:none on file

Five concrete missteps to avoid: lack of a clear why that leadership understands; failing to balance engineering reuse (enterprise apps jump from ~50 to 500 components on average) against company and community value; ignoring the triad legal security governance (CVEs, relicensing risks, who controls a project); weak alignment with developer advocacy and missed inner‑source opportunities; and no sustained executive funding — several major OSPOs shrink or vanish in the last 18 months.

AI-written summary · about

  1. 0:00Introduction
  2. 1:52Open source mainstream growth
  3. 6:24OSPO funding threats
  4. 8:11Misstep: Unclear OSPO purpose
  5. 10:40Misstep: Unbalanced OSPO value
  6. 13:38OSPO structure debate
  7. 14:50Misstep: Ignoring open source risks
  8. 18:51OSPO and developer advocacy
  9. 24:54Inner source strategy
  10. 26:52Misstep: No executive OSPO support
  11. 31:56Selling OSPO to leadership
  12. 33:05Holistic OSPO strategy
  13. 38:10IBM AI Alliance
  14. 41:18Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.