If you look at the OSPO mind map you will see an OSPO may have lots of responsibilities such as "establish and improve Open Source processes", "oversee Open Source compliance", and "eliminate friction from using and contributing to Open Source". Yet a lot of OSPOs only have a few people working on these responsibilities, especially those who just started their OSPO. How do scale your OSPO with a small team?

Automation is the answer, but that raises the question which tools to use for which use cases. In this session, Thomas will show how several OSPOs have been working together to create open source tooling to automate their FOSS policies and processes. He will demonstrate a reference processes for how one can automate 'oversee Open Source Compliance' and 'Publishing a new open source project' from start to finish and some of the lessons he learned on automation over the years.