How to consume & contribute Open Source without an OSPO

An OSPO(Open Source Program Office) is a dedicated team to mitigate risk arising out of Open Source consumption and Open Source Contribution, but not every organisation will have the resources to have one or it may prioritise it later.

So how can an organisation keep a check on the risk and still be able to scale and leverage Open Source. If unanswered, developer team's question about compliance may slow down overall growth of the project and can contribute to copyright infringement.

Having a strategy that answers all of these questions by design can reduce a major chunk of risk. Join us for a conversation on how to get the most out of Open Source with minimal resources.