In recent years, a troubling trend has emerged within the WordPress community—one that threatens the very principles of open source collaboration we hold dear. It’s time we address the elephant in the room: the glaring double standard when it comes to who should bear the costs of WordPress development and infrastructure.

The Automattic Argument

For years, we’ve heard justifications for Automattic’s substantial investments in WordPress. “They benefit greatly from the platform,” the argument goes, “so it’s only fair they shoulder these expenses.” This logic seemed sound—until now.

The WPEngine Controversy

Enter the WPEngine situation. Suddenly, the same voices championing Automattic’s contributions are singing a different tune. Now, we hear cries of “It’s open source!” and “They shouldn’t have to pay anything to use it!”

But wait—doesn’t this contradict everything we’ve been saying?

The Hypocrisy Exposed

This shift in narrative exposes a deep-seated hypocrisy within our community. We can’t have it both ways. Either we believe that those who profit from WordPress should contribute proportionally, or we don’t. There’s no middle ground that isn’t riddled with inconsistency.

A Call for Consistency

It’s time for the WordPress community to take a hard look in the mirror. Are we truly committed to the principles of open source, or are we selectively applying them to suit our interests?

We must establish a consistent philosophy about contribution and compensation in the WordPress ecosystem. Otherwise, we risk eroding the trust and collaboration that have made WordPress the powerhouse it is today.

What do you think? Is it time to address this double standard head-on?