Megan Wilhite – Featured Salt Contributor

March 8, 2017 - Rhett Glauser

The Salt Contributor Profile Series

Starting with just Tom in 2011, the Salt open source community is now comprised of thousands of contributors. While large and vibrant, we are most proud that the Salt community is friendly and inclusive. But the Salt community is only as good as its individual, diverse members, who don’t always get the attention they deserve. So Mike Place, SaltStack software development manager and Salt core lead maintainer, decided to start a SaltStack blog series to profile a new and notable Salt contributor every once in a while. This is the first of that. Introducing Salt contributor Megan Wilhite.

First up, Salt contributor Megan Wilhite, SaltStack QA engineer.

Megan Wilhite

Tell us about your yourself.

My name is Megan Wilhite, or most people refer to me as Ch3LL. I grew up in and currently live in Salt Lake City. I have been working at SaltStack as a QA engineer for about a year and a half now, and before SaltStack I worked in DevOps and systems administration in healthcare and high education.

While working as a DevOps engineer I absolutely fell in love with Salt and the community and this is what drew me to apply to work at SaltStack. In my free time you will most likely find me either playing a video game or drawing and painting.

How have you used Salt?

Before working at SaltStack I used Salt configuration management as a DevOps engineer. Now I use more of the orchestration capabilities of Salt almost every day do things like testing the Salt packages we supply for I am also working to help improve the Salt release process and we use Salt orchestration and Salt Reactor to automate all of those processes as well.

What areas of the Salt codebase are you most focused on, and why?

I am mostly focused on creating and adding tests for the Salt execution and state modules. I also help triage new Salt issues so I get to dive into the code for many different areas of Salt.

What areas of Salt do people not know enough about?

When people think of Salt they often only think of configuration management but I think it is really strong in orchestration and event-based automation. I love using the Salt Reactor system to react to events and to drive even more automation into my processes.

What are your plans for contributing to Salt in the future? 

As a SaltStack QA engineer, I am working to improve Salt QA plans specific to areas where we need more tests. This is done so we can see stability in more areas of the Salt project.