<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Open Source on Romano Roth</title><link>https://romanoroth.com/en/tags/open-source/</link><description>Recent content in Open Source on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Sat, 15 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/open-source/index.xml" rel="self" type="application/rss+xml"/><item><title>The Zühlke Platform Plane: Should It Go Open Source?</title><link>https://romanoroth.com/en/blogs/zuehlke-platform-plane-open-source/</link><pubDate>Sat, 15 Mar 2025 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/zuehlke-platform-plane-open-source/</guid><description>&lt;p>Should we open-source our internal developer platform? That is the question I brought to the audience during this talk. Instead of a traditional presentation, I gave a live demo of the Zühlke Platform Plane and then opened the floor for an honest discussion about the benefits, risks, and realities of open-sourcing a commercial platform product.&lt;/p></description></item><item><title>GitHub DevSecOps Part 4: How to Ensure License Compliance</title><link>https://romanoroth.com/en/blogs/github-devsecops-license-compliance/</link><pubDate>Wed, 25 Jan 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-license-compliance/</guid><description>&lt;p>GitHub does not ship a license scanner out of the box, and when we went looking in the marketplace, none of the existing actions did what we needed. So we built our own with a colleague from Microsoft and published it. In Part 4 of our GitHub DevSecOps series, Patrick Steger and I plug that License Finder action into our Spring Boot pipeline, configure which licenses are acceptable, and show how to surface the results inside GitHub.&lt;/p></description></item><item><title>GitLab DevSecOps Part 4: How to Ensure License Compliance</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-license-compliance/</link><pubDate>Wed, 24 Aug 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-license-compliance/</guid><description>&lt;p>You ship a Java application that depends on Spring Boot, which depends on dozens of other libraries, each with its own license — and most teams cannot tell you what those licenses actually are. In Part 4 of our GitLab DevSecOps series, Patrick Steger and I add license compliance to the pipeline so the question is answered automatically on every commit. The good news: with GitLab Ultimate, this is one template line away.&lt;/p></description></item></channel></rss>