I’ve spent about four years at Red Hat, and now it’s time to move on…
What follows is a bit of historical rambling, and some forward looking statements.
Long-time readers of my blog will know that I was very active in the puppet ecosystem for many years. I learned a lot while writing puppet code, and while building some of my outrageous puppet hacks. Over this time, I had quietly put together some design notes and a prototype for some “future tool” ideas. I had code-named this project “puppet-ng”.
I reached out to Puppetlabs to share some of these ideas in late 2013. Shortly after, during a hiring interview with their CTO, I presented some of my designs, but was told that they weren’t interested.
Around the same time, Red Hat had been showing interest in my Puppet work, particularly around Puppet-Gluster. They offered me a job in their Systems Engineering team, and I accepted.
As part of the Systems Engineering team, we were responsible for glueing different products together. I made the case that the glue that we were using at the time wasn’t effective, and that I had some designs and a prototype for a better mouse trap. A number of great engineers (including the CTO) liked the idea, and so I got to hacking.
|hopefully you'll one day see me as a master artisan with great foresight (read the xkcd alt-text at https://m.xkcd.com/974/)|
I released the first public prototype
in September 2015. As any hacker can tell you, naming is hard,
and so after exhausting all the other ideas, and wishing to avoid a trademark
dispute with Puppetlabs, I settled on
Shortly after, Red Hat acquired Ansible.
Ansible is a fine piece of software, but has a completely different focus than
mgmt. Even in 2014, I was well-aware of Ansible, and even an Ansible
predecessor named func.
As anyone who has seen an
can tell you, they’re completely different in scope. Ansible is an on-demand,
centralized orchestrator, whereas
mgmt is real-time, decentralized automation.
Nevertheless, things slowly got more politically complicated at Red Hat, and it
was impossible to get funding for additional engineers. Ultimately, Red Hat set
my time quota for
mgmt to zero
and assigned me to work on some projects that I wasn’t passionate about.
I’m sad to have to leave Red Hat, but that’s the cost I’ll pay to be able to hack on what I believe in. I wasn’t given the chance to write a “good-bye” email, so this will have to suffice. There are a lot of incredible engineers at Red Hat, and it was my pleasure and privilege to meet and work with so many of you. Hopefully you’ll be able to steal away some of your time to send me patches and help promote my project.
It should be no surprise that I want to spend 100% of my time hacking on
mgmt. I don’t have any clear plan for funding at the moment, so I will be
living off of my savings while I try to get it minimally viable.
I’ve decided to experiment with a Patreon Campaign. It probably won’t amount to a full-time salary, but I’m hoping people will step up and pay for the kind of software that they believe in and want.
Alternatively, if you can’t afford a recurring donation, one-time PayPal donations are appreciated as well. Cash and cheque are fine too if you prefer to avoid fees!
Longer term plans for me and
mgmt are not decided yet, so until I sort out my
future, please give me a shout. I love to chat, and I’m available
if you’d like to hire me to work on
mgmt or to present at your conference.
You can follow James on Mastodon for more frequent updates and other random thoughts.
You can follow James on Twitter for more frequent updates and other random thoughts.
You can support James on GitHub if you'd like to help sustain this kind of content.
You can support James on Patreon if you'd like to help sustain this kind of content.