Description of icon when needed 3 Min Read

In the first of our series on Taking up Vocation, we met three developers who worked on projects in their off time to deliver solutions for common household problems, to log personal journeys, and to help the community measure the value of open source. This time, we spotlight engineers who use their passion for open source to help create better processes and traceability for everyone in the community.

Each of the three engineers we will meet in this installment would characterize their work as a hobby, and vice versa. They are passionate about their contributions to the community for the benefit of all open source projects. Whether keeping tidy inventory of the licenses in containers, pushing a new bug fix for Kubernetes or tracing code to find the most efficient routing in the Linux Kernel, these engineers cover it all.

We are tickled to share these conversations — yet another sampling of the gifted and generous developers in our midst. We look forward to any and all comments and suggestions around what to feature next in this series.

A Bill of Materials for Containers

VMware Open Source Engineer Rose Judge walks us through a demo of Tern, a VMware-originated open source tool that generates a software bill of materials for containers and Docker files. This includes all of the associated licenses for each of the layers and a full summary for the entire container image.

 

 

Which Fixes Make the Patch Release?

Tim Pepper, Senior Software Engineer, talks about Kubernetes patch releases and triaging incoming pull requests. The Kubernetes project provides a major release four times per year, but patches are released far more often. But, how are fixes selected and integrated in the major releases versus the intermittent patch releases? Tim pulls back the curtain to show us the magic in the process.

 

 

What’s Inside That Code?

Author and creator of ftrace for the Linux kernel, Steven Rostedt, shares with us his insatiable analytic curiosity and shows us how to trace his “hello world”code. He knows no limits in delving deeply into the kernel, dissecting technology for as long as he can remember. It may have started when he reassembled broken toys as a child!

 

Stay tuned to the Open Source Blog and follow us on Twitter (@vmwopensource) for more insights and takeaways from our open source developers.