Five for the Future is WordPress's ask of companies that benefit from the ecosystem: pledge 5% of your resources back to the project. In practice that usually means sponsored employee time — engineers and marketers whose work hours are dedicated to WordPress.org contribution rather than company product.
Rocket.net takes this seriously. I'm one of the contributors they sponsor, and that sponsorship covers 23 hours of my working week. This is what those hours actually look like.
Why I Wanted This
I've been contributing to WordPress on my own time since 2023 — patches, testing release candidates, showing up to Core team meetings on Tuesday evenings. At some point the work grew to a scale where doing it properly in the margins felt unsustainable. I wanted to give it the attention it deserved.
I've said this plainly before: "I've always wanted to leave a digital signature behind me within the open-source ecosystem." That's not marketing language — it's the actual reason. Contributing to a project used by 43% of the web is genuinely rare. You get to work on something that affects real people at a scale most engineers never touch.
Where the Hours Go
The 23 hours breaks down across several different contribution areas. Core development is the anchor — reviewing trac tickets, preparing patches for upcoming releases, testing release candidates before they ship. WordPress 6.3 through 6.9 all had my involvement in some form, whether that was a committed patch, a reviewed ticket, or RC testing that caught a regression.
A portion goes to the Hosting team. As someone who works in WordPress hosting infrastructure daily, I care about this team's output in a practical way. We produce compatibility documentation for new WordPress releases, surface hosting-specific concerns to Core, and coordinate testing across different hosting environments. It's the kind of work that's invisible when it's done well.
- Core: patches, ticket triage, RC testing, Dev Chat prep and summaries
- Hosting team: compatibility documentation, Core coordination, hosting-specific testing
- Support: answering questions in the WordPress.org support forums
- Testing: systematic testing for major releases and beta periods
- WP-CLI: testing and contributing to the command-line tooling
Dev Chat Summaries
One responsibility I took on that I didn't expect to value as much as I do: preparing Dev Chat summaries. Every week the Core team meets in Slack, and somebody has to write up what was discussed and share it publicly on make.wordpress.org. It sounds administrative. It's actually one of the most useful things you can do for distributed contributor teams.
Most Core contributors are scattered across time zones. A clear, readable summary of what happened in the Dev Chat lets contributors who couldn't attend stay in sync. It's also a record — six months from now, you can look at that summary and know when a particular decision was made and why. Writing them made me much more attentive to the nuances of what actually gets discussed in those meetings.
If you want to start contributing to WordPress and don't know where to begin, Dev Chat summaries are a real option — it's meaningful work, it's always needed, and it builds your understanding of how Core development actually flows.
What Rocket.net Gets Right
Sponsoring contribution time isn't a cheap marketing exercise if done properly. Rocket.net doesn't direct my contribution work toward things that benefit the company specifically — the commitment is to WordPress.org broadly. That independence matters. The moment sponsored contribution becomes advocacy for the sponsor's product, it stops being contribution and starts being something else.
The fact that a hosting company is investing in the health of the platform it hosts is a bet on the ecosystem. I think that bet is right. And being one of the people executing on it is work I take seriously.
