Michael Stahnke

Michael Stahnke

Michael Stahnke is director of engineering at Puppet. He's held a few roles and been a part of the company growing from 35 to 520+ employees. While staying near the domains of release engineering, operations, and community, he’s been in leadership for most of the last decade. His interests are building teams, mentoring team members, driving change with customers, and playing with his son. He came to Puppet from Caterpillar, Inc. where he was an infrastructure architect, infrastructure team lead, and open source evangelist. Michael also helped get the Extra Packages for Enterprise Linux (EPEL) repository launched in 2005, authored Pro OpenSSH (Apress, 2005), and writes with some frequency about technology and computers. He's @stahnma on Twitter and Medium.

Mapping the Puppet Forge

A long time ago (well, June of this year) the Puppet Forge was running without a leader. In my role as community manager, I saw the Forge as having this awesome potential to be the resource for user-generated content surrounding the Puppet community. I knew it was getting more attention, but that was mostly anecdotal. My next step was to find some data that could tell a good story. Puppet Modules are often the first way people learn and start using Puppet. We’ve had our Puppet Forge for a while, but I didn’t feel like I knew a lot about it. When we were getting ready to interview Product Owners for the Puppet Forge and Modules, I decided I wanted to know more to help me prepare for the interview, and maybe give me some insight into usage patterns that I hadn’t thought about. Like any geek, I love data. I knew we had all sorts of data in our module download logs, but we had not ever really taken the time to transform that data into awesome information. I started with simple awk/sed/grep to find basic information, like what modules were popular. This worked for a time, but then I wanted to know modules by name, find popular authors, and do things like ignore version number changes.
Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.