A Year in Core – 2021

Here’s some aggregate data for 2021 about WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contribution on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. Please note: it only include code contributions and it does not include contributions on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repositories like GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/.

The raw data for this post are on this public spreadsheet. You might find that easier to read if you have low vision or colorblindness; the graphics below are a snapshot pulled together to include as much information as possible in this blogpost.

General Trac overview

In 2021, the WordPress Core team shipped 1852 commits. 2797 tickets were opened, 2732 tickets were closed, and 408 were reopened.

Also, 2572 people contributed to WordPress source code using Trac, and 305 people made their very first contribution to WordPress Core ♥️

Tickets closed236315372147182355248210157882711512732
Tickets reopened263345212537773622193136408
Tickets created2002803711771973202882971611261901902797
New contributors144314223537151218147110305
This chart can be scrolled horizontally

Check out the Trac timeline in the graph below:

Here’s how many props and new contributors the Core project had per month. The most prolific month was November, in the WordPress 5.9 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. cycle, followed by June (WP 5.8 beta cycle).

Components activity

How did 2021’s commits break out by Core Component?

The most prolific components were:

  • Build/Test Tools with 310 commits (17% of all listed commits)
  • Docs with 198 commits (11% of all listed commits)
  • Editor with 188 commits (10.5% of all listed commits)
  • Bundled Themes with 144 commits (8% of all listed commits)
  • Coding Standards with 140 commits (8% of all listed commits)
  • Then comes Media, REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., Code Modernization, External Librairies, Administration, Upgrade/Install, Site Health and Posts/Post Types. The other components each had fewer than 30 commits this year.

Data fetched from WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profiles

The data below comes from matching contributors’ usernames, as mentioned in Trac props, with their profiles on WordPress.org. One caveat: usernames that did not match a profile on dotorg, or that left blank their country/company information, filled in non-exploitable info got ignored. After all, “The Universe” or “The place to be” are not known countries 😆

Contributions by country

The next graph shows the number of props received by country. The top eight countries, based on the number of props received, are these:

  • United States with 1142 contributions
  • France with 266 contributions
  • Russia with 227 contributions
  • The Netherlands with 225 contributions
  • India with 219 contributions
  • Australia with 211 contributions
  • United Kingdom with 112 contributions
  • Canada with 102 contributions

Contributors (people) by country

In 2021, people from more than 56 countries contributed to WordPress Core.

The top eight countries by contributions, expressed as the number of props received, are:

  • United States with 155 people
  • India with 58 people
  • United Kingdom with 34 people
  • France with 26 people
  • Germany with 23 people
  • The Netherlands with 20 people
  • Canada with 16 people
  • Australia with 15 people

Contributions by company

In 2021, people from at least 236 companies contributed to WP Core.

These companies each contributed (well, their people did) to more than 50 commits:

  • Automattic with 785 contributions
  • Yoast with 379 contributions
  • Whodunit with 215 contributions
  • Advies en zo with 191 contributions
  • Bluehost with 146 contributions
  • Human Made with 131 contributions
  • Google with 87 contributions
  • iThemes with 73 contributions
  • Dekode Interaktiv with 52 contributions

Contributors (people) by company

The graph below is also interesting, because it shows that a huge number of companies have only one contributor—or a very few contributors. The exceptions are Automattic, with 85 core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. on Trac in 2021, Yoast (18 contributors) and 10up. Only those three companies had more than ten people credited on Trac in 2021.

What did 2021 hold for Core Committers?

33 Core Committers committed code to the WordPress SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. repository this year:

@sergeybiryukov (729), @desrosj (272), @hellofromtonya (159), @johnbillion (93), @peterwilsoncc (86), @ryelle (61), @audrasjb (59), @noisysocks (54), @joedolson (46), @gziolo (42), @timothyblynjacobs (38), @youknowriad (38), @davidbaumwald (31), @antpb (26), @whyisjake (20), @jorbin (19), @azaozz (18), @jorgefilipecosta (15), @johnjamesjacoby (13), @ocean90 (12), @clorith (10), @spacedmonkey (9), @adamsilverstein (8), @flixos90 (7), @jffng (6), @pento (6), @iandunn (5), @mikeschroder (4), @westonruter (4), @joemcgill (3), @rachelbaker (2), @isabel_brison (2), and @swissspidy (1).

Of the 1852 commits, 729 were made by people working at Yoast, 426 from employees of Automattic, and 272 came from Bluehost people:

Thanks to @marybaum for the copy review and to @flixos90 and @adamsilverstein for proofreading.

#contributions, #contributors, #team-update, #week-in-core, #year-in-core

2015 Contributor Survey

Hi coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team folks! Thanks for all your hard work and contributions in 2015. Could you contribute few more minutes to fill in the 2015 contributor survey? It will help us establish some baselines around the contributor experience so that we can see how things change over time.

**This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.**

The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results by the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could knock it out right after you read this post! 🙂

There are two sections of the survey. The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).

The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.

The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks!

#annual-survey, #contributors

Updated Credits

Each release cycle, we try to recognize those core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. who’ve made the greatest impact, ramped up the quickest, and/or been the most reliable.

In the Contributing Developers categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., mainstays Sergey Biryukov, Dominik Schilling (Ocean90), and Cristi Burcă (Scribu) are joined by Aaron Campbell and Helen Hou-Sandi. Aaron has been contributing for several years, but his work this cycle on improvements to custom headers stood out. Helen, who was a Recent Rockstar in 3.3, stepped up with improvements to the theme screen, UIUI User interface/CSSCSS Cascading Style Sheets. fixes, and general helpfulness as fixes of all sorts were made through the later stages of the cycle.

The Recent Rockstars section is mainly aimed at recognizing newer contributors and/or contributors who’ve been around for awhile casually but have recently increased their involvement. In this category, Amy Hendrix worked (with Aaron Campbell) on the improvements to custom headers with great success. George Stephanis worked on css and improving the mobile experience. Stas Sușkov contributed to the thinking behind HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. captions, a feature that has been waiting patiently on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for years. Max Cutler and Marko Heijnen both worked on updating aspects of XML-RPC, and Kurt Payne contributed to dozens of tickets including the refactoring of adminadmin (and super admin)-ajax.php.

Thank you all for your increased efforts, and congratulations on having your picture in the credits!

#3-4, #contributors, #credits

Organizing Our Contributor Groups

Hi there, core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. (and those who follow them). One of the things I’ve been meaning to do in the contributor community for the last 3-4 years is organize it so that when we say “contributor” it doesn’t just mean coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. code and the different contributing groups can all be on the same page. You may have seen some surveys sent/posted to the forums/docs/theme review teams etc. Your turn!

In order to create a closer relationship between all the contributor groups, ensure our policies and agendas don’t conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved., recognize outstanding contributors, and just generally level up, we need some organization. To wit:

  • I’d like to identify who the active contributors are in each group.
  • I’d like to appoint someone from each group (based on votes from the active group participants) as a group liaison to the rest of the WP project and any cross-team initiatives to improve communication.
  • I’d like to set up a central P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. for communicating project-wide things so that no contributor group ever has to hear important announcements after the fact and we can discuss any issues that come up that could use the help/attention of people from other groups (including core).
  • I’d like to try and set up a monthly IRCIRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. chat and/or Google hangout for the liaisons to have some real-time communication.
  • I’d like to organize an annual contributor summit. Similar to the core team meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. concept, but more inclusive.

The core code contributor team is the most in the know right now, but I’d like to make things a little more equal. Even within core, sometimes I hear people saying they wish they had more of a voice. The way the survey is set up, first you’ll pick how many reps you think core needs to have in the game (just one for core, or a couple, with each representing a different level of experience/seniority to make sure more issues/concerns are heard?), then you’ll vote on who you think the rep(s) should be. Note that inclusion in the survey does not mean that person has agreed to be a rep… I just pulled from our credits list and teams page for 3.4. Once the votes are in, I’ll contact people to see if they’re up for it.

The survey is at http://wordpressdotorg.polldaddy.com/s/core-contributors
and is password protected to help reduce spam responses: core2012

If you could fill it in before the weekend is over (or right now… it’s only a few multiple choice questions), that would be great.


#contributors, #survey

Contributors are no longer shown a bunch …

Contributors are no longer shown a bunch of things that they can’t use, and Contributors/Authors don’t see delete checkboxes or edit links for posts they can’t delete/edit (poka-yoke).

#contributors, #poka-yoke, #ui