“We Came to Stay”
One year ago, ZF published the “ZF Free and Open Source Software Manifesto” (FOSS). In this interview, Sarah Moser reflects on the impact of this milestone – and gives an outlook on what’s next.
One year ago, ZF committed to an increased use of Open Source Software by publishing the FOSS Manifesto. What was the background?
In general, Open Source Software is a key element for developing core functions for the software-defined vehicle efficiently, quickly, and with high quality. We had experience with Open Source for quite some time, but now we wanted to make a lasting contribution. In the Open Source community, credibility matters. Mindset, long-term perspective, and strong anchoring within the organization – these are success factors. We wanted everyone, internally and externally, to know: ZF came to stay. That’s the message we sent with the Manifesto.
What concrete steps have you taken since publishing the FOSS Manifesto?
I’d like to highlight three types of activities: Internally, we created structures to accelerate knowledge sharing and interaction around Open Source. We also obtained a certification that demonstrates our “proficiency” in Open Source externally. And finally, we successfully participated in projects with partners, customers, and even competitors that use Open Source to advance the software-defined vehicle.
What was crucial for internal anchoring?
A central hub is our Open Source Project Office (OSPO). It provides guidance, defines standards, and addresses overarching topics such as cybersecurity in the Open Source environment and intellectual property. We also launched our Inner Source portal, which promotes company-wide collaboration and showcases successful projects involving Open Source.
Inner Source is a common concept aimed at creating an Open Source-like culture within a company. How do you achieve that?
We foster knowledge exchange and reuse of existing code. Our Inner Source portal is linked to training initiatives. We’ve designed numerous courses covering fundamentals like governance and licensing, as well as practical tips on contributing effectively.
How do you measure success?
We see continuous growth in training participation. In October, we hosted our first Inner Source Summit, which attracted over 100 attendees and was a great success in terms of content. These participants are all multipliers for the Open Source community within ZF.
Which projects with external partners stand out?
A prime example is the Open SOVD project – an initiative within the Software Defined Vehicle (SDV) program of the Eclipse Foundation. The goal was to create interfaces enabling signal- and event-driven functions to work across different vehicle platforms. This kind of foundational work is important to us because it allows us to leverage our extensive corporate experience to influence future standards.
Is this still experimental or already relevant for production?
All projects we participate in are relevant for series applications. The results of the Open SOVD project will reappear for many software developers because they are central – whether for ADAS functions, chassis systems, or the transition from traditional ECUs to High-Performance Computing (HPC). Open SOVD simplifies and accelerates all of this.
What remains to be done?
We want to consistently continue on the chosen path and strategically build on the foundation we have established. This means actively collaborating with customers and partners on projects to ensure our expertise contributes to the standards of tomorrow. At the same time, I aim to shape internal structures so that Open Source becomes accessible to everyone supported by practical materials and clear processes. Furthermore, it is important to us to proactively address key future topics such as cybersecurity in the context of the EU Cyber Resilience Act, in order to guarantee trust and security.
