Inside an OSPO: What open source program managers actually do

How OSPOs handle inbound, outbound, and upstream work, and why supply chain attention is a double-edged sword.

Open source program managers are the wheel greasers who make sure developers have the resources they need to get stuff done, whether that’s inbound integration, outbound contributions, or upstream projects. In this episode, Bryan Behrenshausen, Open Source Program Manager at SAS Institute, joins the We Love Open Source podcast to share the three Ps of OSPO work, why software supply chain attention is a double-edged sword for maintainers, and how AI will change developers’ roles without replacing them like calculators didn’t replace mathematicians.

“The opinions expressed are Bryan Behrenshausen’s own and do not represent the views of SAS Institute Inc.”

Bryan’s role boils down to three Ps: Processes, policies, and projects. He handles inbound open source when organizations integrate components into products or infrastructure, consulting on licensing issues and logistics. He manages outbound open source when teams release their own applications or contribute to third-party projects upstream. As the open source wheel greaser, his job is making sure internal parties have resources they need, whether that’s training sessions or policy reviews.

Establishing an OSPO requires finding an executive sponsor who gets it. This champion needs to understand open source’s business value, collaborative value, and what the work takes. They create air cover and institutional space to get stuff done. Working in open source only works when organizations understand the value, and a strong executive sponsor makes that happen.

Read more: Stop guessing, start measuring developer engagement

Software supply chain dominates current conversations. Global concern has made visible work that’s been invisible for years, showing how integrated open source is into digital infrastructure worldwide. But this attention cuts both ways. Proposed remedies for supply chain precarity put undue burden on open source maintainers, many of whom are volunteers or one-person teams without resources to meet increasing global demands. It’s a multifaceted conversation requiring everyone’s attention.

Bryan’s advice for getting started: Just get involved. Engage projects thoughtfully, humbly, and respectfully. No contribution is too small. See a typo in documentation? Fix it. Opportunity to localize a button? Do it. Jump into code reviews with ideas nobody else is considering. People will help when you engage the right way.

On AI replacing developers, Bryan draws a calculator analogy. AI won’t replace developers any more than calculators replaced mathematicians. Will AI change the role’s nature? Sure, just as democratizing technologies changed roles throughout society for generations. Replace is too strong a word for our future.

Key takeaways

• OSPO managers handle the three Ps: Processes, policies, and projects for inbound integration, outbound releases, and upstream contributions. Success requires executive sponsorship from someone who understands the business and collaborative value.
• Software supply chain attention is a double-edged sword: Making invisible work visible is great, but proposed remedies burden volunteer maintainers and one-person teams who lack resources to meet increasing demands.
• Get involved thoughtfully and humbly: No contribution is too small. Fix typos, localize buttons, offer ideas in code reviews. People will help when you engage respectfully.

Bryan’s message: Find champions who create space, recognize supply chain complexity, and engage projects humbly regardless of contribution size.

More from We Love Open Source

• 15 open source backup solutions to protect your data
• The AI slop problem threatening open source maintainers
• Why 1.3 billion people depend on progress, not perfection
• Stop guessing, start measuring developer engagement
• 5 forces driving DevOps and AI in 2026