The WordPress project is run by a core leadership team and led by co-founder and lead developer Matt Mullenweg. The team governs all aspects of the project, including core development, WordPress.org, and community initiatives.
Trusted contributors and core developers earn their stripes on more than their abilities and actions. Leadership roles are earned on the basis of professionalism, personality, attitude, and respect among peers.
The best contributors naturally respect and subscribe to the project’s core philosophies. A lack of a personal agenda is paramount: we’re all a part of the same community and we all share common goals. This doesn’t mean you can’t have an opinion – far from it. The best contributors can balance their opinions with the goals of the project and the perspectives of both users and developers. Offering consistently good suggestions, demonstrating a strong ability to collaborate with others, and being able to accept (and provide) feedback are all important.
You can identify these standards in some of our best core contributors, and that’s why they have strong influence over the project. Final decisions are made by the core team, which has evolved over the life of the project based on merit.
The WordPress project is led by the core leadership team, which consists of WordPress co-founder Matt Mullenweg, five lead developers, and a number of core developers with permanent commit access.
The lead developers are Helen Hou-Sandi, Dion Hulse, Mark Jaquith, Andrew Nacin, and Andrew Ozz. These developers have final authority on technical decisions, and lead architecture discussions and implementation efforts.
Rachel Baker, Pascal Birchler, Sergey Biryukov, John Blackbourn, Jeremy Felt, Andrea Fercia, Boone B. Gorges, Drew Jaynes, Aaron Jorbin, Joe McGill, Gary Pendergast, Dominik Schilling, Mike Schroder, Scott Taylor, Weston Ruter, Ella Iseulde Van Dorpe, and Aaron D. Campbell are permanent core committers.
WordPress has a number of contributing developers. Some of these are former or current committers, and some are likely future committers. Regardless, these are trusted and veteran contributors to WordPress core who have earned a great deal of respect among their peers.
As needed, WordPress also has guest committers, individuals who are granted commit access, sometimes for a specific component, on a temporary or trial basis. Michael Arestad, Felix Arntz, Mel Choyce, Joe Hoyle, Konstantin Kovshenin, Eric Lewis, Tammie Lister, Ryan McCue, James Nylen, Konstantin Obenland, Adam Silverstein, and Peter Wilson are currently guest committers.
Other contributing developers include Michael Adams, Nikolay Bachiyski, Jon Cave, Daryl Koopersmith, Joseph Scott, Andy Skelton, Matt Miklic, Peter Westwood, Lance Willett, and Samuel Wood.
The core and contributing developers serve as guides for WordPress development. With every version, hundreds of developers contribute code to WordPress. These core contributors are volunteers who contribute to the core codebase in some way. All it takes is a single patch to make a difference.
The support forums are run by a team of volunteer moderators who remove spam, handle disputes, and generally keep the peace. They are led primarily by a self-appointed team leader and everyone is encouraged to jump in.
The Documentation team is responsible for all things documentation, including the Codex, handbooks, developer.wordpress.org, admin help, inline docs, and other general wordsmithing across the WordPress project.
This handbook and the Codex are the primary sources of information for learning how to develop, improve, and troubleshoot WordPress. The handbook is curated by a small group of volunteers, while the Codex is open for anyone with a wordpress.org user account to edit.
Themes submitted to the WordPress Themes Directory are reviewed by a team of volunteers to ensure compliance with the WordPress.org theme guidelines. The team is made up of community leaders and contributors who work together on developing standards and reviewing themes.
Plugins submitted to the WordPress Plugins Directory are reviewed by a team of volunteers to ensure they meet WordPress.org guidelines before being included in the plugin directory. The team rep is Boone Gorges, with volunteers Pippin Williamson, Scott Reilly, Samuel Wood, Mika Epstein, Kailey Lampert, Daniel Bachhuber, and Mark Riley (Reviewer Emeritus) reviewing plugins and developing standards.
WordPress core development updates and discussion from the teams above happen on the Make WordPress blogs. You can also follow core development by joining the #core channel on the project’s Slack team, which is open for anyone to join. Dedicated channels are set up for various WordPress core components and community initiatives. A more specific breakdown of the WordPress project’s communication channels is available in the Communication section of the Core Handbook.