-
AuthorPosts
-
-
-
Interesting that three of the OSS contributions that WP Engine takes credit for as contributions, are actually acquisitions (Local, Advanced Custom Fields, Genesis). Unless I’m missing something? Seems disingenuous to take credit for that.
I don’t agree with everything Matt said about WPE, but I do agree with the spirit of it. Big money has distorted OSS for a long time to serve its own ends, and will continue to do it as long as money is on the table. We must call it out and find solutions that serve the common good.
I’m grateful that OSS is still a place for lively and good-faith debate about important issues. Above all else, I want the community to focus on transparency, driving the outcomes that help the most people, and consistency in applying standards / criticism. I don’t trust private equity much, but I believe there are smarter and more diplomatic ways to list our community than some of Matt’s tactics. This is not new for him — he’s impassioned, speaks his mind, sometimes talks out his butt, and seems to be willing to reconsider his strongly held views. That is enough of what I want in a leader to satisfy me, though we must continue to question power in all its forms, even (especially) in people we admire.
Finally: as a WP professional since 2009, it’s far more confusing to explain WordPress.org vs. .com to a businessperson than it ever would be to explain WP Engine’s branding. They may be using WP trademarks improperly, I dunno, but it’s never confused a single person I’ve met.
-
Matt Mullenweg delivered yet another insightful and thought-provoking presentation at WordCamp US 2024! His bold vision for the future of WordPress, combined with spicy takes on AI integration and community-driven development, left us all inspired and eager to see what’s next. Truly a must-watch for anyone passionate about the evolution of WordPress! 🚀🔥 #WordCampUS2024 #WordPressInnovation
-
-
It’s worth being clear that the screenshot in this article with “WordPress Engine” highlighted is a partner bio page. The content is managed by the partner in question, in the same way any sort of profile bio is. It is wrong to hold that aloft as evidence of WP Engine going out of their way to misrepresent themselves or intentionally infringe the WordPress trademark.
It’s a mistake and it should be removed/amended. No more.
-
To clarify, the screenshot showing “WordPress Engine” is from a partner bio page, and the content is managed by the partner, similar to how a profile bio works. It’s inaccurate to use this as proof of WP Engine misrepresenting themselves or violating the WordPress trademark. It’s simply an error that should be corrected or updated, nothing more.
-
The irony of Matt writing that “What WP Engine gives you is not WordPress” because they disable Revisions is pretty thick, considering his own WP VIP disables big image resizing (and doesn’t even document that they do so). It’s easy enough to re-enable in code, but c’mon — just admit this is about WPE’s failing to support the ecosystem and not about revisions being turned off or WordPress being “hacked” and “butchered.”
-
-
AuthorPosts
- You must be logged in to reply to this topic.
