Saying goodbye

31 May 2016

Reposted from Drupal.org

When I started on the last day of March 2014, I could never have guessed at how challenging and rewarding this role would be. That is why it is incredibly hard to say that my last day with the Drupal Association will be June 10th.

For more details read, Reorganizing for a changing Drupal.

In looking at our structure with the leadership team, Holly, Matt and I saw that our roles did not fit in a smaller, more focused Drupal Association. It is no easy decision to include yourself in proposed cuts. I can’t say how proud I am to be part of a group willing to make that sort of sacrifice for something in which they believe.

Drupal is a strong community

Drupal.org is a complex site and with a reduced engineering team, they will need to focus on mission critical services and find new ways to work with the community to continue to make the site great for contributors and evaluators.

With help from the rest of the team, I wrote a post called The Drupal.org Complexity that tries to take all of the complexity that surrounds our Git repositories and their integration with projects and issues on Drupal.org and describe it in a way that begins to show just how amazing our tools are. (I have yet to find a project with more total contributors to a single version of the code.)

Our smaller team is going to need to focus on sustaining services like testing, packaging, security updates, etc. They will be updating the Drupal.org roadmap with a more narrow focus.

I personally believe in the power of Drupal as an engine for amazing. And so much great stuff is still in store for the community.

Thank you

Firstly, thanks to my family for putting up with the crazy hours, and travel that required bedtime calls at 6 in the morning—at least we had fewer pager calls in the middle of the night. Even when there were challenges, I always had your support. (And I’m looking forward to a little summer vacation together.)

Thank you to the board of directors for giving me this chance to help a project I love strengthen its home. Drupal.org is more professionalized and easier to maintain while continuing to scale up to the needs of the community. You took on tough discussions—and helped us make even tougher decisions. Being a board member is a huge commitment that you all took seriously while still being a blast to hang out with during and after each board meeting.

Thank you to my leadership teammates (Holly, Megan, Matt… and Joe too). The were some great times and some hard times. We weathered so much together with a commitment to making the best choices we could with the information we had. I can’t put into words how much I appreciated being surrounded by such a great team.

Thank you to my engineering staff, or tech team, or Drupal.org team—whatever we are calling ourselves this week. You’ve taught me a ton every day. I loved sharing technical challenges with you all. I’m confident this was one of the smartest teams I will ever have the chance to lead. Every single one of you have admiration. Thank you for letting me be your “umbrella” for a bit. I hope our careers cross paths again and again.

The entire staff at the Drupal Association is such a phenomenal group of humans! You’ve made going to work each day fun and exciting. You showed what it means to have passion and lived the values of a great community.

Lastly, I also want to thank the Drupal community members I was able to meet both in-person and virtually over the past two years. You are truly committed and passionate. Thank you for being patient and accepting and generous.

Thank you.

What’s next?

In the next two weeks, I’ll be documenting systems to help with the transition. Specifically, the team and I will write additional posts about our testing infrastructure (DrupalCI) and our new Composer endpoints.

I’ll also be working very hard to help staff that are impacted by the layoffs land softly at new opportunities. If you have opportunities at your company or organization, please contact me if you are interested in some of the best Drupal talent on the market. I’m confident they won’t be available for long.

I hope to announce my own next steps shortly. I plan to keep involved in the community. Drupal has been a big part of my career, but it is not the only technology that has shaped it. Drupal will continue to be an important part of my toolkit for helping companies, governments, and organizations of all types delivering solutions that are complex and need to scale.