On 9 April 2026 we sat down at Contributor Day at WordCamp Asia in Mumbai, for the first time. By the evening we had sent in our first translations and opened our first pull request, at the Core AI table. Nothing was approved or merged that day. Somebody has to read the work first. A week later the first translations were approved, and the pull request was merged. Of the strings submitted that day, 17 were eventually approved: 15 in Hindi and 2 in Urdu. That was all. The day itself is a story of its own.
This post is about the six months that followed, from April to the end of September. It is not a scorecard. ShifteQ is a Mumbai-based web agency. We earn from WordPress every day, through client websites and custom plugins, and for years we never contributed directly to the project. This is what contributing looked like once we started. We are writing it down in case it helps someone else start.
How it started: one pull request in a month
In April, exactly one of our pull requests was merged: the one from Contributor Day. It corrected a page of testing instructions in the AI plugin. It took a week.
That is what starting looks like. You do not arrive and fix WordPress. You find one small thing that is wrong, you send a correction, and you wait to see whether anybody wants it.
Somebody did. In May there were 17. In June there were 25.
What we did: mostly small things
By the end of September, 73 of our pull requests had been merged across WordPress and WP-CLI. Most of them were small. 32 were documentation. Most of the rest fixed one behavior each.
We say this on purpose. People stay away from open source because they think it needs a brilliant idea. Almost none of this did. It needed someone to read a page, notice that a step was wrong, and fix the step.
What went where
- Handbooks, 32. The pages people follow when something is broken: updating over FTP, FileZilla, must-use plugins, loopbacks, server configuration, caching.
- The AI plugin, 21. Fixes to how its features behave when something is missing or goes wrong.
- Other WordPress projects, 14. The test runner that hosts use, Playground, Openverse, Plugin Check, Blueprints, Gutenberg and WordCamp.org.
- WP-CLI, 6. Fixes to commands that scripts depend on.
Not everything was on GitHub. We handle Hindi for 7 plugins so far, and all of them are above 90%. We published 24 block patterns and 4 photos. And we went back into the room four more times: three local meetups and WP Future Conclave in Kozhikode.
How it changed things
Counting pull requests says we were busy. It does not say that anything changed for anyone. These are the ones where something did.
Someone had been waiting
34 open issues were closed by our pull requests. 14 of them were more than a year old, and half of those had been waiting for more than three and a half years.
The oldest was opened in August 2018. WP-CLI did not handle empty input properly when importing users. Somebody reported it, and then it sat there for almost eight years.
The fix was merged six days after we sent it.
That gap is the reason for this post. The work was not hard. It was waiting for somebody to pick it up.
A screen stopped crashing
One day after WordPress 7.1 came out, we found a way to crash an admin screen. A percent sign in the tooltip text of a plugin was enough.
- Before: a button labeled "Save 20%!" brought the whole screen down. A label that said "100% done" came out as "1000one".
- After: both show exactly what the plugin author wrote.
We reported it as ticket 65914. The lead of one widely used plugin confirmed that its users were already hitting the crash. The fix was committed with our props and shipped in WordPress 7.1.1 on 17 September.
Features stopped failing silently
In the AI plugin, several features did nothing when no AI provider was connected, and did not say why. Now they say that a provider is missing. Slug Generation could do nothing at all and still look as if it had worked. Now it applies the slug, or says that it did not.
Tests stopped passing by mistake
Hosting companies run the WordPress test suite on their own servers and send the results back. The tool they use counted a run with a missing or empty results file as a success. Now that run fails loudly, which is what a test is for.
Someone else finished what we started
In August we sent a small fix towards a WP-CLI issue from 2019: WP-CLI quietly ignored a mistyped option instead of warning about it. Our part was only the groundwork. The lead maintainer of WP-CLI took the rest over and merged the warning itself on 13 September.
We count that as the best thing that happened in these six months. You do not have to finish a problem to help solve it.
What it gave back
23 of the 73 were merged within 24 hours. The fastest took 33 minutes. That speed is not ours. It belongs to maintainers who read a patch from someone they have never met, on the same day it arrives. The slowest took 121 days, and that is fair too. Reviewers are volunteers.
It worked the other way as well. Five bugs that we reported were fixed by somebody else, GoDaddy among them.
And on 19 August, WordPress 7.1 came out with one of us in its contributor credits. After sixteen years of using WordPress, that is a strange and good thing to read.
Thank you
Nothing here was merged by the people who wrote it. To every reviewer, maintainer and committer who read this work, corrected it and merged it: thank you.
Contribute when you can
The numbers were never steady. June had 25 merged pull requests. July had 4.
And that is fine.
Contributing is not a job you have to show up for every day. You can spend a weekend fixing something, disappear for a month because life or client work gets busy, and come back when you feel like it. Nobody needs you to contribute full-time, keep a streak going, or explain why you took a break.
Do what you can, when you can. Even one small contribution is worth making.
If you have been meaning to start
You do not need permission, and you do not need a big idea.
- Translate one string into your language.
- Fix one sentence in a handbook that confused you.
- Find an older issue that looks manageable. There are plenty waiting for someone to take a look.
Our first month was one pull request that took a week. If yours is too, you are exactly where we were.