The WP Engine dispute has shown how much we expect from WordPress.org without thinking about who pays for it.

The response to the restriction

When Matt Mullenweg restricted WP Engine’s access to WordPress.org resources, people were furious. I think we’re overlooking what those services cost.

What costs money

  1. Servers aren’t free: Data centers charge real money to host code, regardless of whether it’s open-source or not.
  2. Bandwidth isn’t infinite: Every time you hit that “Update WordPress” button, someone is paying for the bandwidth.
  3. Maintenance isn’t magical: Keeping updates working takes time and money.

Hosting companies know this

I find it hard to accept a hosting company expecting free infrastructure while charging its own customers for hosting. It knows those services cost money.

Who pays the bill?

My first reaction was to wonder who had been paying all along. I hadn’t thought enough about it, and I’m grateful someone did.

What happens when we ignore the cost

If we expect everything free and don’t consider who does the work, we risk:

  1. Discouraging contributors who invest time and resources
  2. Making it harder to keep WordPress services running
  3. Expecting others to do work we won’t support

What I’d like us to do

  1. Acknowledge the costs: Next time you use a WordPress resource, take a moment to consider who’s paying for it.
  2. Show gratitude: Thank the individuals and companies that make WordPress possible.
  3. Contribute if you can: Whether it’s time, money, or expertise, find ways to give back to the community.
  4. Educate others: Help spread awareness about the real costs behind our “free” platform.

These services need people and money to keep running. I’d like us to spend more time figuring out how to support them.