Core Team Details Expanded: August 2024

In addition to the primary dashboard, this page offers additional information and context on the information shared in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team dashboard.

Core Commits in GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ (January to August 2024)

This chart represents commits in the wordpress_develop and 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/ Repositories in January – August 2024.

Core Pull Requests in GitHub (January to August 2024)

This chart represents pull requests in the wordpress_develop and Gutenberg Repositories in January – August 2024.

Core Pull Requests in GitHub (January to August 2024)

This chart represents issues in the wordpress_develop and Gutenberg Repositories in January – August 2024.

Last 90 Days TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Ticket Graph (July – September 2024)

Here’s a graphic representation of the 90 day Trac Ticket graph, showing tickets opened, reopened and closed.

Progress Towards WordPress 6.7

Progress towards WordPress 6.7 in Trac, as measured on September 11, 2024.

Total number of tickets: 412 – closed: 169 – active: 243

Contributor Insights for Core Repositories (past 10 years)

The core repositories in GitHub saw spikes in activity around 2017 (related to Gutenberg), 2021 (potentially related to Phase 2). However, as of late August, there seems to be an overall lull in contributions compared to past years, which might be temporary.

GitHub Issue Closing Efficiency (January to August 2024)

Across the Core and Gutenberg repositories, there is a median closing time of 6.073 days for issues. These repositories have a steady rate of BMI (Backlog Management Index) , defined as the number of closed issues divided by the number of open ones in a given period of time – which is essentially the efficiency of closing issues. Lead time is the time expressed in days between the initiation and completion of closing an issue. Shown in average. Our Backlog Management Index is Trending towards 0.8, which means that there re more open issues compared to closed ones.

GitHub Pull Request Closing Efficiency (January to August 2024)

Across the Core and Gutenberg repositories, there is a median merging time of 0.974 days for pull requests. There is clear indication of a reasonably steady REI (Review Efficiency Index, defined as the number of closed pull requests divided by the number of open ones in a given period of time), as well as reasonably steady lead times of around 50 days, barring spikes. However, REI seems to be having a downward trend (0.93), at this time with a value of 0.89 around the end of August, showing that there are more open pull requests compared to closed ones.

Attracted Developers

In general, this chart shows a high volume of attracted developers. There are clear tri-yearly spikes, which likely coincides with WordPress releases, showcasing returning developers. We are seeing a clearly spike in 2024 as well as a spike around 2018 (Gutenberg launch).

Overall Contributions

There is a clear and steady increase in overall contributions in our GitHub repositories. However, a lull around August is evident in these contributions.