Something has shifted in how our ecosystem talks about Individual Identity in WordPress. We used to credit the person who wrote the code. Now we credit the logo on their paycheck. Call it architectural debt in the culture, and it is starting to show in how we contribute and how we ship.
I have been around since the 4.x days, long enough to watch this project go from a hobbyist community to a corporate-sponsored machine. Sponsorship pays for the lights, no argument there. But we have ended up with a system where the “Company” field outranks the “Contributor” field. When a core developer feels their unpaid, spare-time patch counts for less than a corporate-pledged hour, something in the community core is wrong.
The badge problem is a design logic error
A “Self Employed” label on a WordCamp badge caused a stir recently. Small thing, but it is a bad UI choice sitting on top of a bigger one: why is the company name the primary identifier? We are software people. Our Individual Identity in WordPress is the username, the personal site, sometimes the hometown.
Badges used to put the human first. Now they put the sponsor first. Nobody did that on purpose, it fell out of the push for corporate involvement. If you are wearing a company t-shirt, I already know who you work for. I would rather have the URL of the project you are proud of, or your .org handle, so I can follow what you actually do.
Measuring inputs instead of results
How we measure success is a bottleneck of its own. Five for the Future celebrates “hours pledged,” but an hour is an input. In development nobody asks how long a function took to write. We ask whether it performs and whether it solves the user’s problem.
Putting participation and process ahead of results has produced a race condition in our workflows: more people involved, and things somehow moving slower. Fred Brooks described this in The Mythical Man-Month back in 1975, when he wrote that adding manpower to a late software project makes it later. Choose inclusive consensus over decisive execution and the communication overhead eats the productivity.
If you want the constructive version of this argument, my thoughts on the WordPress contribution pipeline get closer to a fix.
The cultural refactor
Treating Individual Identity in WordPress as a secondary transient has to stop. The spare-time volunteers built this house, and the credit belongs to them. Without them this is just another corporate CMS.
- Change the Five for the Future testimonials so they say what shipped instead of how many hours were pledged.
- Put personal websites and .org usernames ahead of corporate affiliation on the badge.
- Check whether the extra participation is moving us toward the goal or only generating more process.
The question I keep coming back to is “How have I been complicit in creating the conditions I say I don’t want?” It is easy to keep your head down on the ticket and ignore the culture around it. But the culture is the infrastructure, and good code will not save you if that is crumbling.
For the numbers behind how the project is changing, there is my analysis of the WordPress Core numbers.
If the identity and credit side of your WordPress work is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
Where I land on this
The strength of WordPress has always been its individuals, and our systems should show it. Reward impact rather than activity, and credit people rather than logos. That is the version bump our community values need.
