Thirteen years ago today, I received my very first props for contributing to WordPress Core. If my WordPress contribution journey were a person, it would now be a teenager. It’s pretty wild to think about, but I’ve now been contributing to the WordPress project in some way for a third of my life!
What is a “prop”?
In the WordPress open source project, community participants receive credit for contributing to a given change or deliverable by receiving “props.”
Props should be given to all those who contributed to the final commit, whether through patches, refreshed patches, code suggested otherwise, design, writing, user testing, or other significant investments of time and effort. Usernames are parsed for the credits list and WordPress.org profiles.
The names of all the contributors who helped make a specific release possible are collected in the weeks leading up and added to the Credits API, which powers the Credits page in the WordPress dashboard.
To date, I have been listed on the Credits page for 24 consecutive releases starting with 4.7, and 29 of the 35 releases overall since my first credited contribution in WordPress 3.6 “Oscar”, alongside 224 other contributors.
Every year is a bit different than the last, but I can confidently say that this past year has been significantly different. What it means to develop software or contribute to open source is changing rapidly with advanced AI innovations seemingly every day combined with these tools being accessible to more people than ever before. But throughout all this, one truth holds strong: open source software is more important than ever.
Looking Back
It seemed only fitting for me to instruct AI to analyze my contribution activity over the last 365 days to try and find anything interesting!
Prompt
Today is the 13th Anniversary of my first credited contribution to the WordPress project. I try to write a blog post each year to mark the occasion.
I’m looking for ideas for this years edition. Please go and read all of my past posts (accessible here at this category feed https://jonathandesrosiers.com/category/contributing-anniversaries/feed) and give me 10-12 ideas for what to focus on this year. You can also look through the other content on my site for other ideas.
After you do that, I want you to look at the git history for the
wordpress-developandgutenbergrepositories between July 8, 2025 and yesterday (July 7, 2026). I want you to parse the logs to summarize my activity and find some particular ways to analyze the data that are interesting.Be creative! These posts are the most fun when I am able to find some unique insight into a year’s worth of contributions.
Results
Your year 13 in numbers (Jul 8 2025 → Jul 7 2026)
| Metric | Value |
|---|---|
| Core commits authored & committed | 119 (~7% of all 1,707 core commits this cycle) |
| Additional commits crediting you (props received) | 97 → ~216 credited touch points in core alone |
| Lines changed | +41,746 / −21,940 across 656 file-changes |
| Unique Trac tickets | 69 |
| Gutenberg PRs authored | 24 (+108 co-authored/credited) |
| Reverts you committed | 6 |
The headline: 80 of your 119 core commits (67%) are “Build/Test Tools.” Add Tests + General and it’s ~80%. You spent year 13 as the plumber of WordPress — CI, build pipeline, dependency stewardship, release infrastructure.
The most interesting angles the data surfaced
- The nocturnal committer. ~50 of your commits land between midnight and 4am. Tuesday (37) and Thursday (31) are your peak days; Saturday is nearly dead (3).
- The month that didn’t exist. January 2026: zero commits. March 2026: 40. Your cadence is a heartbeat synced to the 6.9 and 7.0 release cycles, not the calendar.
- The June 30th ritual. You bumped Gutenberg’s pinned hash seven times in a single day (v22.8.0 → v23.4.0) — a whole quarter of catching-up compressed into one sitting.
- Supply-chain quiet work. Pinning full-length action SHAs, replacing abandoned third-party actions, migrating release logic to a GitHub App, ca-bundle updates — you spent the year hardening the software supply chain nobody thanks you for.
- Keeping the ancient libraries breathing. lodash, underscore, backbone, getID3, Twemoji — you’re the caretaker of WordPress’s legacy vendored code.
- Future-proofing the matrix. MySQL 9.5/9.6/9.7, MariaDB 12.1, PHP 8.5 (HEIF/HEIC) — you test tomorrow’s platforms today.
- A first, quietly historic commit: “Include example for disclosing AI usage” — you helped write core’s early AI-disclosure norms.
10–12 ideas for the year-13 post
- “The Plumber’s Year: 67% of My Commits Were Infrastructure.” Own the unglamorous. A love letter to build/test/CI work — the contributions that never show up in a release announcement but without which nothing ships. This is your strongest, most authentic angle.
- “Confessions of a Nocturnal Committer.” Fun, human, data-driven: your midnight-to-4am commit cluster, Tuesday/Thursday peaks, the dead January. Chart your year as a heartbeat and reflect on what it says about maintainer rhythms (and sustainability/burnout).
- “216 Times.” Companion to your 2024 props post, flipped: this year you received credit ~216 times in core (119 committed + 97 propped). Explore the two halves of a committer’s fingerprint — the work you land yourself vs. the work you shepherd for others.
- “The Boring Commits That Keep 40% of the Web Safe.” The supply-chain security angle: pinned SHAs, abandoned-action replacement, the GitHub App migration, ca-bundle. Frame maintenance-as-security — timely and underappreciated.
- “I Test the Future So You Don’t Break in It.” MySQL 9.7, MariaDB 12.1, PHP 8.5 — a piece on being the person who runs tomorrow’s platforms against today’s code, and why the test matrix is a form of care.
- “The Commit I’m Proudest Of Was One Line About AI.” Use “Include example for disclosing AI usage” as a springboard into how WordPress (and you) navigated AI’s arrival in the contribution workflow in 2025–26. Very of-the-moment.
- “Anatomy of a Revert.” Six times this year you reverted your own or others’ work. A candid, senior-contributor essay on why reverting is a feature not a failure — iteration, humility, and trunk stability.
- “A Year in Dependencies.” The stewardship story — lodash/underscore/backbone/getID3/Twemoji. What it means to be the caretaker of code written a decade ago that you can’t just delete. Legacy as responsibility.
- “Who I Built With.” Refresh your collaborator lens for year 13: westonruter (24), jorbin (22), johnbillion (15), peterwilsoncc (14), wildworks (13)… Name the people behind the props lines and tell a story or two about the work you shared.
- “The Shape of a Release Cycle, Drawn in Commits.” Overlay your monthly commit counts on the 6.9 and 7.0 timelines — the March spike, the December bundled-themes push, the quiet stretches. Show readers what a maintainer’s year looks like mapped to what shipped.
- “Same Job, New Tools: Automating Myself Out of the Loop.” Your Gutenberg PRs are almost all release automation — GitHub App auth, GHCR publishing, reproducible builds, Dependabot. A reflective piece on spending your labor building the machine that does the labor, and what that means for the next generation of contributors.
I haven’t validated any of these numbers, but they do seem relatively accurate at first glance. I had ChatGPT create an embroidered patch that reflects the summary above.
And some of those writing suggestions are pretty good ideas! I’m out of time for today, so I’ll file these in the backlog for another day. But here’s to another year of helping the world find their voice to share their stories using WordPress. 
Past Milestones
“Props” Anniversaries: Ten, Eleven, Twelve (archive).
Commit-iversaries: Two, Five, Six, Seven (archive).
Featured image credit: CC0 licensed photo by Mark Westguard from the WordPress Photo Directory.
The post 13 Years Contributing to WordPress appeared first on Jonathan Desrosiers.