Coordination is usually the harder half of an open-source project, not the code. Nominations for the WordPress Core Team Reps 2026 edition are open, which is a good moment to notice that a small group of people does the administrative work behind every major release.
Francesca Marano, Jb Audras and Benjamin Zekavica have held the role for the past year. They work as facilitators rather than leads. Dev Chat stays organized and cross-team updates actually get written because those three put in the hours, and that is most of the reason the project looks stable from the outside.
What WordPress Core Team Reps actually do
People often read “Team Rep” as “Team Lead.” The project avoids that second word on purpose. The rep job is administrative and centered on communication rather than technical direction, so the person writing the most commits is not automatically the best representative.
What that involves in practice:
- Posting the Dev Chat agenda, hosting the weekly chat, and making sure a summary gets published afterwards.
- Watching the bi-weekly Gutenberg releases and the major Core milestones.
- Reporting quarterly updates back to the wider WordPress project.
I have written before about WordPress contribution talent and what it would take to support that pipeline properly.
The technical side of keeping up
Reps still have to track the moving parts of the project. The role is mostly administrative, but anyone doing Core management should keep WP-CLI within reach for a quick audit of which version each environment is running. It takes seconds and keeps you close to the code.
# Check the current core version and check for updates
wp core check-update
# See the status of the current environment
wp core statusHow the 2026 election works
Nominations are open now. Put yourself or a colleague forward in the comments on the official Make WordPress Core post. A nomination is not a commitment: the final poll only lists people who agreed to run.
Nominations close January 31, 2026, at 23:59 UTC, and a two-week vote runs in early February. The handbook spells out what the Team Rep role covers if you want the official version.
Governance changes leave marks on the project. I went through the numbers on that in an earlier post on how to decode WordPress Core numbers and read them as a health signal.
If tracking WordPress Core Team Reps news is eating your dev hours, I can take it off your plate. I have been wrestling with WordPress since the 4.x days.
Should you put your name in?
Being one of the WordPress Core Team Reps costs about two hours a week, and it is what lets everyone else get on with building products. The work is administrative and mostly unglamorous. If you have those two hours, say so before January 31.
