Getting Commit

I received commit to WordPress this past week.

The past couple days have been a bit of a haze — Community Summit on Wednesday and Thursday, WordCamp US Friday and Saturday (where I presented with the wonderful Courtney O’Callaghan), and then yesterday’s Contributor Day. I found out on late Saturday night, at a bar, completely by accident, that I was receiving commit. The new batch of committers were formally announced the next day during Matt’s State of the Word. I join a short list of designers with commit access. I am one of now five women who can commit.

Screen Shot 2015-12-07 at 1.18.31 PM

I was given commit with the reassurance that I would not be expected to do a lot of committing (I think this was told to console me when I started looking a bit green). Committing, I was told, was a sign of trust. It was a sign that the lead developers team trust me enough to help guide the future of WordPress that they have granted me the access to change it. I am honored to receive that trust, especially as a designer. I’ve come along way since my first patch was committed by Andrew Nacin, just over three years ago.

I was instructed to commit something by the end of yesterday’s Contributor Day. Gary found me an easy fix to commit (removing an extra word from documentation in Twenty Eleven, of all things) and walked me through the commit process. Then, I committed my first change to WordPress. It was familiar to how I’m used to committing code for work, but infinitely more terrifying. Afterwards, I felt a little nauseous.

I’m joined in this new privilege along by a great set of folks. Congratulations to the other six people who received commit this week: fellow designer and Automattician Michael Arestad, Rachel Baker, Joe Hoyle, Eric Lewis, Mike Schroder, and Pascal Birchler.

Sound fun? You too can get involved with WordPress at https://make.wordpress.org/.

One thought on “Getting Commit

  1. Pingback: WordPress commit – Michael on webby stuff

Leave a Reply