New Committers!

Usually, new committers are announced in line with release cycles, but we were all just too excited to wait until the 4.8 cycle started, so here they are!

First up, James Nylen (@jnylen0). James has been a driving force on the REST API, both when it was a feature plugin, and more recently in Core since the endpoints were merged. The tickets and comments he leaves on Trac are always thorough and thoughtful, his patches are consistently excellent, and his attitude is exemplary.

Next, Adam Silverstein (@adamsilverstein). Adam has been a regular contributor for years, bringing significant improvements to the Media Grid, as well as handling large parts of the JavaScript work around the REST API endpoints – both in wp-api.js, and tenaciously working on porting Dashboard features across to using the endpoints.

Rounding out our guest committer list, Felix Arntz (@flixos90). Felix has been a contributor to Multisite for some time now, writing excellent patches, as well as running Office Hours and Bug Scrubs. Not only that, he’s always been willing to jump in and help in any area of Core, showing the same level of enthusiasm and consideration across the board.

Finally, we have a bumper class of guest committers to make make permanent! Pascal Birchler (@swissspidy) and Joe McGill (@joemcgill), Rachel Baker (@rachelbaker), and Mike Schroder (@mikeschroder) are now permanent committers.

Please join me in congratulating James, Adam, Felix, Pascal, Joe, Rachel, and Mike! 🎉🔥⭐️👻💯

#4-7, #commit

Commit announcements for 4.7

Happy 4.6 release day! Commit announcements for 4.7 are brief.

Andrea Fercia (@afercia) is now a permanent committer. Andrea’s work with and on the accessibility team has helped WordPress make huge strides forward, and he’s wielded his commit powers quite effectively over the past few releases. Please join me in congratulating Andrea. 🎉

All other guest committers have been renewed for the cycle. Looking forward to 4.7!


New committers for 4.6!

Each cycle, the lead developers review guest and potential committers. We’ve been taking the time to assign each new committer a dedicated mentor and ensure we’re getting feedback from and giving it to existing committers, so it took us a little longer to put it all together this time around. Without further ado, we’ve got two new guest committers and two new permanent committers!

First up, we have Joe McGill (@joemcgill), whose work on responsive images both as a plugin and post-merge has proven invaluable over the last few releases. He has also been serving as a component maintainer for the extensive media component. I look forward to his continued work in this area, as well as other features and parts of core.

Next, Peter Wilson (@peterwilsoncc) will be joining our Australian contingent of committers. Peter has shown solid judgment and admirable tenacity in chasing down tricky issues across a number of areas, especially as we’re approaching the finish line. The trickiest things always get left for last, and help in those areas is always appreciated.

Finally, I’m happy to announce that Ella Van Dorpe (@iseulde) and Weston Ruter (@westonruter) are now permanent committers. Their continuous stewardship of the editor and customizer respectively have been exemplary, and we have all been enjoying the great strides that have been made in these areas thanks in large part to them.

Please join me in congratulating everyone!

Update: Additionally, all current guest committers have had their commit renewed for the cycle.


Welcome the 4.5 class of committers!

As announced in the State of the Word this year at WordCamp US by @matt, there are seven new committers to introduce.

Many of you have seen Michael Arestad‘s (@michaelarestad) design and front-end development contributions over the last couple of years, notably with the redesign of Press This in WordPress 4.2. His numerous, high quality contributions are a welcome addition to core. I personally am looking forward to his work on markup and styling, having relied heavily on his judgment for quite some time now.

WordPress 4.4 adds a new embed feature to WordPress, making it an oEmbed provider for the first time. Work on this new feature was done in a large part by Pascal Birchler (@swissspidy), who has been doing great work for the past few releases. Pascal’s clear communication and thorough support of the flow mindset are things we can all be inspired by.

Rachel Baker (@rachelbaker) is the co-lead of the REST API, a Comments component maintainer, and a major contributor to WordPress 4.4. Her work has made it possible for sites around the world to utilize the REST API, making WordPress a great application platform. Look for more of these contributions as the REST API iterates within core.

Likewise, Joe Hoyle (@joehoyle) is a major contributor to the REST API. As we prepare to commit the REST API endpoints in an upcoming WordPress release, there will be more and more to come from both him and Rachel.

As a Media component maintainer and a long-time contributor across many components and features, Mike Schroder (@mikeschroder) helped shepherd the responsive images feature plugin into core for WordPress 4.4. He was also a backup release lead for WordPress 3.9.

Throughout the WordPress admin interface, everywhere you look you’ll see the work of Mel Choyce (@melchoyce). Her design and experience contributions are long-standing and have benefited the entire ecosystem. As one of the maintainers of the Dashicons project, the icons you interact with daily are a big part of her contributions, as well as themes available in the Theme Directory.

Eric Andrew Lewis (@ericlewis) has been contributing in various forms for many years, exploring lesser-known areas, documenting them, and challenging assumptions. Most recently, you may have seen his work as a Media component maintainer or with the shiny updates feature in WordPress 4.2.

Additionally, Ella Van Dorpe (@iseulde), Konstantin Obenland (@obenland), Weston Ruter (@westonruter), Tammie Lister (@karmatosed), Andrea Fercia, (@afercia) and Ryan McCue (@rmccue [that’s one M, two C’s]) have all had their guest commit renewed.

Please join me in welcoming this great set of new committers!


🎉 One more committer for 4.4!

Please join me in welcoming a new guest committer for WordPress 4.4 — Ryan McCue (@rmccue)!

Ryan has been contributing to the WordPress world for many years, through various patches, as well as being one of the maintainers of the SimplePie RSS library that WordPress uses.

More recently, he started the WordPress REST API feature plugin, and has been leading the development of it for the past two years, nine months and five days (not that anyone is counting!). As the REST API comes closer to being ready for merge, Ryan having commit access is a natural progression: he can bring his expertise in the REST API directly across to WordPress Core.

Congratulations, Ryan! 🎆💯⭐️⭐️⭐️⭐️⭐️

#4-4, #commit

And the other guest committer for 4.4 is…

Now that he’s back from holiday, please join me in welcoming @afercia as a guest committer for the 4.4 release cycle! Andrea (pronounced the proper Italian way) has been invaluable with the huge strides the accessibility of WordPress has taken over the past several releases, lending his experience with accessibility methods and software and tenacity in iterating on patches. He’s also contributed many patches outside of accessibility changes as he’s gotten to know various parts of core. We’ve had a hard time keeping up with all of his work in such an important area of web development, so it’s our pleasure to hand him a set of reins to keep it going.

In core Trac, we have many components and a number of what we’ve come to call focuses. Focus areas include things such as accessibility, UI, and JavaScript, and span multiple components, if not all of them. Building up expertise and trust in a component or focus is critical to maintaining WordPress over time. Commit access is a wonderful thing, but even as committers, we rely heavily on the recommendations of component and focus maintainers to keep tickets and patches moving. Without them, we’d get a lot less done. Andrea is a shining example of how this flow can dramatically improve a specific area of WordPress in a relatively short period of time with continued plans for improvement, and we want to see more and more of this happening. If you’d like to get started with maintainership, please join us in the #core Slack channel and ask about it.

Congratulations, @afercia!

#4-4, #commit

New committers for 4.4!

It’s that time again… Please join me in welcoming Tammie Lister (@karmatosed) as a guest committer for WordPress 4.4. There’s another committer to be announced, but we thought we’d wait until he’s back from vacation for a proper welcome.

You may recognize Tammie from her role as an admin on the theme review team, and she’s also a theme developer extraordinaire at Automattic. Tammie will be heading up development of the new default theme, Twenty Sixteen.

The lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed. Ella Van Dorpe, Konstantin Obenland, and Weston Ruter, all new committers at the beginning of the 4.3 cycle, have been renewed for 4.4.

Over the last few cycles, both Aaron Jorbin and Jeremy Felt have been working through long-term plans, smashing through tickets, and improving the entire codebase, especially when it comes to tests and multisite. I’m happy to announce that both are now permanent committers. Please join me in congratulating everyone!

#4-4, #commit

New committers for 4.3!

Please join me in welcoming three new guest committers for WordPress 4.3 — Ella Van Durpe (@ellatrix), Konstantin Obenland (@obenland), and Weston Ruter (@westonruter)!

Ella has been one of our very top contributors of late. She started with a front-end editor plugin, which parlayed into substantial core editor contributions, including inline image editing in 3.9, inline oEmbed previews and improved editor scrolling (“focus”) in 4.0, distraction-free writing (“focus v2”) in 4.1, and a few dozen other things I am sure I am missing (like this). She’s a powerhouse.

Obenland, well, is also wearing the release lead hat for 4.3. I said plenty of nice things about him there. 😄 While there’s no requirement for a release lead to be a committer, a) it does help with housekeeping, and b) Konstantin has unquestionably earned this in his own right, regardless of his other role.

Weston has been essentially leading the customizer component since his work last year on bringing widgets into the customizer. His body of work there is nothing short of incredible and we’re lucky to have had him spearheading this important work.

The lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed — Aaron Jorbin and Jeremy Felt have both been renewed for 4.3.

We (well, I) neglected to announce that John Blackbourn (@johnbillion), Boone B. Gorges (@boonebgorges) and Gary Pendergast (@pento) were made full, permanent committers at the start of 4.2. John, Boone, and Gary all destroyed it in 4.1 (which is perhaps more obvious now that some of Gary’s work has been trickling out into the open).

Congrats all! 🎉

#4-3, #commit

John Blackbourn is leading WordPress 4.1 (and announcing new committers!)

I’m pleased to share John Blackbourn (@johnbillion) is the release lead for WordPress 4.1. But please hold your applause until the end, I have a few announcements to get through!

WordPress 4.1 will be kicking off at WordCamp Europe this weekend. As noted yesterday, the first meeting will be at 1400 UTC on Monday, September 29.

You’ve probably seen John in action over the years (his first contribution was more than seven years ago). I’ll also add it’s pretty awesome that @simonwheatley and @s1m0nd of Code for the People (a six-person shop) jumped at the chance to donate a large chunk of John’s time through the end of the year back to the WordPress project. (See also this post for more on the release lead role.)

New committers for WordPress 4.1

As many of you know, the lead developers review and appoint new committers to serve each release cycle, often to work on a particular component or feature. This guest commit access comes up for review after each release and can be renewed. I in particular work closely with every guest committer, providing feedback.

I’m pleased to announce our largest guest committer class ever: Gary Pendergast (@pento), Boone B. Gorges (@boonebgorges), Konstantin Kovshenin (@kovshenin), Aaron Jorbin (@jorbin), and Jeremy Felt (@jeremyfelt).

Konstantin and Gary both enjoy diving into internals and getting their hands dirty with tough bugs and regressions. Jeremy will be continuing to push multisite forward. Jorbin will be focusing on testing and tooling. Boone has been working on a set of great improvements to tax, date, and meta queries, with test coverage to come with it.

These five should be strangers to no one — they’ve all been around the community for years, and not only are they top-notch contributors who embody the project, but they’re generally just really good people.

This will also be John Blackbourn’s third release as a guest committer. I’d also like to welcome back Ian Stewart (@iandstewart), who previously was a committer during the development of Twenty Eleven, and will be back to take the commit reins for the next default theme, Twenty Fifteen.

Scott Taylor (@wonderboymusic) was on fire during 4.0, especially if this terrific post is any testament, continuing a great run. Scott’s WP origin story is pretty great — right as he was getting ready to leave the WordCamp San Francisco 2011 after-party, @koop convinced him to stick around a little longer. We were introduced, and not long after (from the party) his first patch got committed. A thousand contributions later that have made an indelible impact, Scott is now a permanent WordPress committer. We hope to have him around for a long time.

About a year ago Drew Jaynes (@DrewAPicture) was given commit access to lead the hook documentation effort. This was hugely successful. After the effort was complete, Drew’s role evolved into maintaining all inline docs, which has just been wonderful. We appreciate his attention to detail and his dedication to this never-ending effort. Drew is now a permanent committer.

Congratulations to John, Drew, Scott, Gary, Konstantin, Jeremy, Jorbin, Ian, and Boone!

#4-1, #commit, #release-lead

Helen is the WordPress 4.0 release lead

Mike and I are pleased to pass the release lead baton to Helen Hou-Sandí for WordPress 4.0. I don’t think this will come as much of a surprise to most of you, but please offer @helen your congratulations, which are well-deserved.

We’ve already discussed 4.0 a bit in our last two meetings. Expect today’s weekly meeting at 2000 UTC in #wordpress-dev to be the kickoff for WordPress 4.0.

@DrewAPicture, @wonderboymusic, and @johnbillion have all been renewed for guest commit for 4.0. Additionally, I’m happy to announce that, after more than a year as guest committers, Dominik (@ocean90) and Sergey (@SergeyBiryukov) both have permanent commit access. Their prolific contributions have left a lasting mark on WordPress and I hope to see them at it for years to come.

A release lead, if anyone is curious, determines all important parameters for a release, like schedule, deadlines, which feature plugins are merged, and more generally, scope and goals. They take point when it comes to meetings, shepherding contributions, announcement posts, and updates. A release lead is a connector and facilitator, identifying bottlenecks and friction wherever they may be and at the service of the developers and plugin teams that are aiming to have something in a given release, and be in frequent communication with them.

The release lead should should follow what’s being committed, and set the tone for prioritizing and gardening the milestone on Trac. Given the constraint of time in hitting a date, help with prioritization and ensuring good communication lines are two of the most valuable things a lead can contribute.

The last five release leads were lead developers, but that’s not a requirement, nor is being a committer. I always thought of my “code reviewer” and “committer” hats as being separate, additional responsibilities. (Helen, of course, also wears these same hats.) Regardless: the release lead has the final call on all important decisions related to the release.

Addendum: For those unaware, for WordPress, version 4.0 sounds like a “big” version number but it’s just another major release for us, like 3.9 and 4.1, constructed over the same ~4-month release cycle. But don’t tell Helen that! Here’s to 4.0 being awesome.

#4-0, #commit, #release-lead