If WordPress is to survive, Matt Mullenweg must be removed
joshcollinsworth.com
joshcollinsworth.com
He thinks the world has all the historical understanding and nuance of the situation. Why would they?
This looks like a world record speedrun attempt (any%) at destroying a legacy.
It's worth noting that WPEngine looked like this all the way back in 2011: https://web.archive.org/web/20110112043959/http://wpengine.c...
They have never pretended to be anything else.
Why now, Matt?
I didn’t know (or really care) about this battle, but I’ve always passively seen Matt as one of the insightful grandfathers of the blogging era, having insights from the observations from his perch.
This blog post erased that.
I've always felt he was an asshole but could never ground that to a concrete observation. Now I'm certain of it.
Then why comment on it?
Which turned out to be blatantly false, quelle surprise
I'm currently asking @photomatt elsewhere what his plans are to help others lift the load from wp.org by way of supporting alternate plugin/theme repositories. I'll keep you posted.
To the foundation? Ok, then work with them to create a mirror and share the load. Even publicly shamed them into doing so.
Do what's good for the community and product rather than engaging in this embarrassing spat.
Please correct me if I’m wrong here (in any way).
Not a lawyer, but talked about it at length with a trademark attorney when having to defend over the years. It was conveyed that if we aren't willing to legally defend a mark, we could potentially lose it.
It's an interesting take, given that the three board members of the WordPress Foundation are Matt and a ... managing partner of a PE firm (the third is a retired coder, I believe).
"We offer WordPress hosting" is a perfectly legal thing for people to say if they actually offer WordPress hosting, and no amount of trademarks can prevent that. This is specifically called out to try to avoid trademark fuckery.
Sure, everyone refers to the "Big Game" versus the "Super Bowl", but that's largely because the NFL can afford more lawyers than they can, and it's not worth the fight.
A claim I've heard is that the for-profit company has the exclusive commercial license (along with the right to grant sub-licenses).
That sounds about right, and is what's written on the WordPress Foundation's trademark page [1]:
> If you would like to use the WordPress trademark commercially, please contact Automattic, they have the exclusive license. Their only sub-licensee is Newfold.
I read something different [2] while reading up on this whole debacle:
> The WordPress Foundation was launched in January 2010. Automattic transferred the trademarks later that year in September. As part of the transfer, Automattic was granted use of WordPress for WordPress.com, but not for any future domains. Matt was granted a license for WordPress.org and WordPress.net.
I wonder if something changed along the way.
[1] https://wordpressfoundation.org/trademark-policy/
[2] https://wordpress.org/book/2015/11/the-wordpress-foundation/
a) the nonprofit owns a trademark
b) gave an exclusive license with right to sublicense to a for-profit
c) which appears to be run by the same person
d) who is demanding of a competitor to sublicense the trademark
e) paying the money to the for-profit, not the nonprofit
f) when it's not clear that the competitor is infringing on the trademark in the first place.
The litigation here is not likely to go Wordpress or Automattic's way, I think.
And referring to that transfer as "very above board" makes it sound like you're talking about the same thing as the commenter above when in fact you're talking about different things. Because however gracious you find that decision to be, that's a different subject than whether it's above board to, subsequently commingle those responsibilities. And whether or not you feel it's practical, in some sense, it doesn't seem to have anything to do with anything. Either Automatic has The authority to collect licensing payments on behalf of WordPress or they don't and that should be reflected in a charter or something, somewhere.
I don't think referencing the history of Automatic previously owning the trademark has anything to do with anything in this context.
But a cursory glance at Google results for "Wordpress hosting", "woocommerce hosting", or "managed wordpress hosting" will lead you to hundreds of results from a plethora of web hosting companies that have been doing this, many for more than a decade.
The Wordpress Foundation (that owns the "Wordpress" trademark) has not taken any legal action against any of these companies for precisely the same use it's accusing WPEngine of. A judge could well rule that they have not defended their trademark and this claim holds no water.
From reviewing the code, this is not "attribution" in the sense of "here's who wrote this code" but specifically and literally an partner code.. aka an affiliate code or what we'd normally call "a setting"
As GPL'd software, they cannot prevent people from modifying this code and - if they do - Automattic's only counter is to complain about it.
Further, since it's a revenue-generating code, it should be disclosed in the README, etc of the plugin and changeable via the Admin. It doesn't appear either is true.
Ref: https://github.com/woocommerce/woocommerce-gateway-stripe/pu...
It does look like they fixed just a few months later, though: https://web.archive.org/web/20111001085943/http://wpengine.c...
(How fun to see the selling point "Digg-Proof Scalability")
What's the modern soon-to-be-obsolete equivalent?
Pretty sure that Wordpress logo is just the stock logo that came with every Wordpress installation. The name wp engine was the website name of that Wordpress installation.
Matt claims he has been privately discussing with WP Engine for ~18 months about their level of contribution. Automatic contributes the equivalent of 75 full time employees to WordPress and WP Engine contributes 1, despite the companies being comparable in size.
Matt’s actions may have been bad for optics, but I do not fault him for using the resources at his disposal to correct what he sees as injustice.
Of course, there are consequences to using said resources inappropriately.
But perceptions are downstream from actions in a smoke/fire kind of way, and it shouldn't be used as a way to get out of answering for actions.
The public perception seems to be against him, and managing public perception is important.
[1] https://www.reddit.com/r/ProWordPress/comments/1cv15mt/would...
That sounds like an injustice to me. That sounds like someone who has been using Automattic and WP.com (and Pressable), WP.org, and the Foundation interchangeably, depending on what best fits his needs.
So it's possible that that's the answer there.
The trademark license also cannot prohibit nominative usage - that's protected. If you actually, factually offer WordPress hosting, you can say so, in those exact words. You may need to call out somewhere (and WPEngine does) "WordPress is a trademark of the WPF", but no license can prohibit you saying so. What they can't (but don't) say, is anything that implies that they are WordPress - which is exactly why Matt is trying to make some big deal in his head that "my mom thought they were us" (while ignoring the elephant in the room of "Well, wordpress.COM isn't WordPress, either, it's just a licensee", because of course, nobody could be confused by that).
I wasn't expressing an opinion one way or the other, regarding the validity of the trademark infringement.
Now I finally know what they do and offer!
Look - I agree. However, there is not a single person that thinks twice about buying an Android or iPhone handset because it might not be contributing fully to upstream Linux or BSD. People don't care. They don't question it because this is the norm, and frankly neither should Matt if he's going to disagree with the terms of a license he's not qualified to change.
Even the Open Source community doesn't really care that much. Selling modified versions of a program is not inherently a violation of GPL, or even the intent of free software. Matt's disproportionately vocal uproar kinda proves that the only people who care in this instance are the ones trying to profit off Free Software. He's not being righteously cavalier, here - he's being courageously wrong.
If he were just the leader of the WordPress foundation, this whole thing would just be an embarrassing PR failure. As it is, I wonder if his actions will rise to the level of criminal.
After watching his interview with The Primeagen, it seems like he is mentally wearing the clothes of a righteous prophet…the misunderstood advocate of a disrespected organization.
Unfortunately, he’s ignoring the fact that he invested in WPE years ago, is CEO of a direct competitor, has publicly said he hopes WPE loses billions of dollars as a result, apparently has no proof in writing, and is pulling thousands of innocent developers into his petulant crusade.
> Afterward, I also privately shared with [ThePrimeagen] the cell phone for Heather Brunner, the WP Engine CEO, so she can hop on or debate these points. As far as I’ve heard she hasn’t responded. Why is WP Engine scared of talking to journalists live?
this is not normal.
> I have kept my personal philanthropy private until now.
> This is something I’ve tried to keep quiet, because true philanthropy isn’t about recognition.
...
> If Lee Wittlinger, who controls Silver Lake’s investments in the WordPress ecosystem, or Heather Brunner, the CEO of WP Engine, would like to publish their charitable contributions over the past 12 years, they are welcome to do so.Is he trying to avoid turning charity into a pissing contest, or is he trying to use his affluence to shame a competitor? This guy literally can't keep his story straight over the course of a single blog post.
I though part of Matt's point was that Automattic "gave back" to the foundation?
He is not even close to a journalist, he is a dumb tech bro. I hope Heather blocked his number. This is insanely scummy and stupid behavior from Mullenweg.
I also loved how this was formatted, it was quite long but easy to read with a nice font.
Now, I know that's all a bit of a reach, but it's hard for me to not think asking for Matt to be removed for this reason is just like all those people who ostensibly would want public transit to be funded for all those other people who can't afford cars, until they finally got around to ripping up the street you use to drive to work every day and jacked up your taxes by $50.
But, all that said, I've also never liked WordPress at all and don't have a dog in the fight, this is just a thought experiment. However, if I had to move because my landlord eventually got screwed for not reporting my rent on their income tax, I'd be like "well sometimes that happens, was nice while it lasted but my place was a shithole, they weren't competing fairly, and they were constantly showing up to city council meetings trying to block a mid-rise from going up while I was at work paying their mortgage".
However, my question is this: has WPE given a factual rebuttal to Matt's claims? Especially, considering that their entire business is dependent on WordPress?
I am concerned that in the eagerness to judge Matt's conflict of interest, we should not throw out the baby with the bath water.
Matt’s position is (ostensibly) based on his hard line views about the moral obligation to contribute created through the use of open-source. The trademark sideshow is based on Matt’s understanding that a moral argument isn’t going to convince a private equity backed company to spend money they don’t need to spend. Matt believes WPEngine has a moral obligation to contribute and the trademark licensing fee is the easiest tool he has to force action.
Matt is making a moral argument. WPEngine don’t care because they’re driven by money not morals.
Given the lack of reliable information right now, I’m going to believe the individual that has a decades-long track record indicating that they care about open source over the private company that is legally obligated to pursue profit as its only objective.
If WP Engine had acted in good faith, Matt wouldn’t have had to come up with terms unilaterally.
Who gives a shit, it doesn't matter. Why would he think WP Engine would pay anything they're not contractually obligated to pay?
This has all played out similarly elsewhere, e.g. to the point that some companies have started to carve out a new types of licensing so that all of the "open source revenue" doesn't just get vacuumed up by the big clouds/hosting providers (e.g. see the "Fair Source" movement being promoted by Elastic and others).
Matt could have gone down that route. I could easily imagine a million ways he could have handled this better and gotten the community on his side. Instead he's acting like a collosal asshole.
Reminder: https://www.wired.com/2011/06/skype-silver-lake-evil/
Also, the whole point of open source is that you don't "own it" after it's open sourced. If you don't like those terms, license them under different ones, which exactly what the whole recent "Fair Source" movement is about and what other companies like Sentry have handled in a much more dignified fashion.
WP Engine was banking on the free stuff from Wordpress.org, and they got burned because they bit the hand that was feeding them.
Matt has shown he simply can't be trusted to keep his roles as head of WordPress Foundation and Automattic CEO independent.
The point of the article is that it's precisely these actions that have damaged the integrity of WordPress for everybody, because we can now no longer look at WordPress as having stable stewardship, but as something ready to whimsically descend into unpredictable retaliatory actions, without any rhyme or reason or structure.
Once you start talking that way, it seems to me you've completely lost sight of what it is to be the healthy steward of a norms driven foundation. The reason you work out things in charters, and in terms of service and so on is precisely to avoid situations like this, where there are spirals of escalation all hinging on subjective interpretations of everything.
... the Managing Partner of one of those evil PE firms.
If they want to play hardball about what’s required instead of acting generously, like Matt has done for decades, then they are getting their just deserts.
Matt isn’t obligated to be nice to dick heads. WordPress.org isn’t obligated to provide service for free.
WP Engine decided that they would only do what’s good for them. Fine. If they piss in the pool, they can’t be mad when everyone else gets out. It is irrational for WordPress to continue acting like there isn’t an extractive entity in their midst.
I can't help but notice that once it gets to the question of whether there's any actual authority to demand a licensing fee, the conversation stops being about what is or isn't legal, who is authorized to do what, considerations of proportionality or collateral damage or any of that, and just start slipping into this mode of speaking like mobsters from the 1920s. If that's the cadence you find yourself slipping into it might be an indicator of whether you're the good guy.
Well, in some sense, he is, at least as it relates to his leadership of WordPress Foundation. As a charity with a mission to support the WordPress community, his actions over the past week look like a singular attack on the community in order to benefit the for-profit Automattic.
This comment on a previous post puts it better than I could: https://news.ycombinator.com/item?id=41661086
And, if Matt had not chosen to be an asshole, would this issue have gotten the prominence that it has got?
Also, WPE could easily have taken the wind out of Matt's sails by declaring their (direct or indirect) commercial support for WordPress.org while reducing to pay money to Automattic. As far as I know, they have chosen to not do so.
For all I know, Matt may lose the battle; but, open source would lose the war if companies and individuals continue to use the kind of arguments that WPE and it's defenders are making - that, they are legally not obligated to care two bits about the open source software on which their entire businesses are built, leave apart what is moral.
The idea that users of open source software "owe" something back to the original developers is revisionist history, and if you don't like how users are using your software, why did you open source it with a permissive license in the first place? There are plenty more restrictive licenses (e.g. GPL) that support a more "if you take you have to give" model. Saying "well, we wanted to open source it but not that kind of open source" is BS.
The issues here are precisely the actions by Matt, so it is reasonable to conclude that had Matt not caused those issues by acting as he has, the issues would not exist.
> open source would lose the war if companies and individuals continue to use the kind of arguments that WPE and it's defenders are making - that, they are legally not obligated to care two bits about the open source software on which their entire businesses are built
I don't believe this to be true, but if it is, the responsibilities lies with Matt for allowing it with permissive licensing and trademarks. Neither WPEngine, nor you or I, are obliged to care about what Matt wants us to care about, or to obey Matt's decrees, and the sole reason is Matt's actions.
The same guy running a for profit company?
If we agree that to be true, then WPE should also be considered evil, shouldn't it? Then, why so much defence for them and all vitriol for Matt?
And, if we accept that WPE are right to focus only on the legality of their action, then should we not apply the same logic to all corporations when they focus on maximizing their revenues and profits?
I mean... The article talks about this extensively. And the article is my first exposure to the issue but presumably it's not the first place where these points have been presented. The authority or obligation to give back isn't a legal one, the authority to demand 8% raises all kinds of conflict of interest issues and appears dubious if not outright illegal, the global message posted to admin dashboards was an abuse of power, and the banning from using plugins doesn't even pretend to have a legitimate pretense.
Apparently part of the backstory here is there's a dizzying context, and there might be some subjectivity involved in surfacing these as the pertinent issues, but I wasn't left with the impression that the ball is in WPE's court to explain any kind of smoking gun that hasn't been accounted for by the discussion in the article.
The article is trying to manufacture consent with vague authority: "Most reasonable and knowledgeable people seem to share this opinion." While it is someone who is not impartial. He claimed that he worked in WPE before and than 'extensively' writes why it shouldn't matter - without telling anything.
I'm not saying that what 'Matt' did is OK. Seems to me no party here is in right. But that is not my point. My point is that these kind of articles - especially lengthy vague ones - are just increasing the drama.
The author makes all kinds of specific arguments that don't have anything to do with consensus, and the structure of the arguments is grounded on the inherent rightness or wrongness of interpretation of various rules, the existence are non-existent of copyright, the disproportionate and escalatory choices Matt has made, a whole host of specific arguments that don't have anything to do with where the consensus falls.
They do mention that Matt has appeared to have turned many in the community against him, but the arguments are pretty freestanding even if you want to set that aside, and there's also another interpretation other than manufacturing consent which is simply that it's a legitimate observation about what's really happening.
I can't say for sure, but there's so much more going on here that's more specific to the issue of right and wrong within zooming out and saying "gosh this sure is a lot of drama". I think if that's the level at what you're engaging in the conversation it's just making everything fuzzier.
But this whole debacle is what happens when a CEO doesn't do that. There can be unexpected, company-ending results.
It is perfectly possible to have a distinct voice without setting the house on fire. There is a middle ground.
Another set of eyes, not to rewrite it into safe corporate speech, but just as a safety guard to say “hold up there bud… Stop and count to 10”
Talking about “counting to 10”, you don’t hit the publish button right away, save it as a draft and leave it a few hours/over night and come back to it when your not as fired up. Hitting publish when your fired up is rarely a good thing.
If you want to vent, swear and shout. Write that angry post, but then select all and delete it, take a breath, and start again. 9 times out of 10 you are going to be a lot less fired up the second time around.
Granted the last two require some self control, but that’s what the first one is for.
As you said, CEOs are human too, and as humans we all need a helping hand every once and awhile, nothing wrong about that.
WordPress, the for-profit company, may be too intertwined with WordPress the 501c3 foundation. I'm not a lawyer, but a nonprofit is supposed to be very careful about how it operates. Matt's post on wordpress.org is clearly crossing the line by blending the for-profit company, with the nonprofit foundation. Perhaps it's not illegal, but it is certainly unethical.
He disabled millions of wordpress sites from being able to update/access things. Plugins.. functionality.. Sure, they don't deserve to get free API access and all that; none of that matters.
What about non-profits for animal shelters, programs like st judes, things where livelihoods depend on it and they don't even know what an API or domain name is let alone what all this stuff is about and their whole stream of operations comes crumbling down because they paid somebody to set it all up for them and all they know to do is long in to wp-admin and press 'update' and make blog posts and check their 'payments' etc and modify/add things like their woo commerce plugins?
We're smart, we know what all this means, a lot of people I come across in the real world can utilize wordpress because it's easy for them, but if I explain in depth how things work they look at me like I'm speaking a foreign language.
He doesn't care.
I don't need that question answered. I already know.
I don't have an opinion on it, but when 75% of the internet is running wordpress, have some tact.
Second, WP Engine can create their own repository of plugins to update their customers' plugins instead of relying on Wordpress.org.
Third, WP Engine customers can just leave to another host if WP Engine can't actually provide the service they are selling.
So much drama.
Especially if they have a fraught relationship with the provider of those free services.
System76 provides the PopOS repos that are based on Ubuntu. They don’t freeload.
Canonical provides the Ubuntu repos that are based on Debian. They don’t freeload.
WP Engine is freeloading, no doubt about it.
If the bandwidth/infra costs to support all of WPEngines customers were so much, then they must have, right?
If they were asked and refused that's certainly one thing. If they were never asked, and then when they refused the demands for money.. then it looks like matt was just looking for a wrench to hit them with and this one came to mind.
No need to ask someone with common sense who is already doing it.
At least for Ubuntu, the packages they distribute generally don't have the same checksum as Debian, so they're not the same packages (at least as binaries).
Also, "wordpress.org" is hard-coded as the plugin repo source all over WordPress.
Go talk to other people who've had dealing with Matt and you’ll find plenty who don’t agree with that statement
If any of this is true why is it so surprising that wpe was cut off?
> WP Engine wants to control your WordPress experience, they need to run their own user login system, update servers, plugin directory, theme directory, pattern directory, block directory, translations, photo directory, job board, meetups, conferences, bug tracker, forums, Slack, Ping-o-matic, and showcase. Their servers can no longer access our servers for free. The reason WordPress sites don’t get hacked as much anymore is we work with hosts to block vulnerabilities at the network layer, WP Engine will need to replicate that security research on their own. Why should WordPress.org provide these services to WP Engine for free, given their attacks on us?
If they worked there for that long perhaps they can provide insight into the upstreaming of issues strategy or if it was an org focus or an afterthought?
And this is not the first time he does it, so this is nothing new and he is not the only one.
Rich people and big companies do this all the time, but Matt is doing in public.
Let me guess you want another Mark Zuckerberg in there?
What's wrong with you people? He needs a stern talking to, not complete removal. This is another re-occuring case of "create hero, destroy hero" where the public likes to build someone up, find a flaw with them, act like they are irredemable, act like you're so distraught and hurt by their behavior, cry your tears, and destroy the hero you once celebrated.
He's getting one from his customers.
EDIT: Yep - https://techcrunch.com/2021/10/19/automattic-tc1-origin/
He’s got to go.
>Five for the Future asks that if you benefit from WordPress, you give back 5% of your time directly to that open-source project
As someone that semifrequently has to support WP installs, I would definitely make a case for it not being a benefit in my life
It’s also just about a Rails clone for PHP.
The first thing I think cannot be neglected to be mentioned in posts about the dispute is that (1) Matt created the project (yes, a fork counts), (2) his friend coined the name, (3) Matt's company originally registered the trademark. Then (4) Matt's company donated the mark to a foundation to make it widely available for noncommercial use while they retained the exclusive commercial license to the mark. No mention of this in this presentation.
To be fair to commentators, part of the trickiness surrounding this dispute is an old issue regarding open source projects: do the open source software licenses imply a trademark license? The answer is generally understood to be: no. Having a license to software does not grant you a license to a trademark. For more on this I found illuminating the 2009 article in the International Free and Open Source Software Law Review by Tiki Dare JD (Director of Trademarks at Sun Microsystems, Inc.) and Harvey Anderson JD (General Counsel of the Mozilla Corporation) titled "Passport Without A Visa: Open Source Software Licensing and Trademarks": https://www.jolts.world/index.php/jolts/article/view/11/37
As one is not given a license to the trademark, a common understanding is that one can:
– limit one's use of the trademark to nominative or descriptive fair use (A)
– use the mark under supplemental guidelines from the trademark owner (B)
– acquire a dedicated license to the trademark (C)
At https://wpengine.com/plans (take your screenshots now) they have titled services they offer simply "Core WordPress", "Essential WordPress", and "Enterprise WordPress". It could be claimed this branding exceeds nominative use. It is far beyond the mentioned descriptive use of a "managed WordPress hosting company". If this branding exceeds fair use, it needs to comply with justifications (B) or (C). It very clearly does not comply with the published guidelines, both before and after recent modifications, that read "All other WordPress-related businesses or projects can use the WordPress name and logo to refer to and explain their services, but they cannot use them as part of a product, project, service, domain name, or company name…". You can also see examples of use (current/cached and perhaps somewhat inadvertent) of "WordPress Engine" itself at https://www.google.com/search?q=site%3Awpengine.com+%22wordp...
Many commentators seem hung up on the fact that using the letters 'WP' was and remains an allowed practice according to (B). However, with regard to any trademark guidelines it could safely be assumed that a mark owner is not suggesting that one may use protected marks in ways that cause confusion as this is counter to the purpose of trademarks. Commentators are likewise hung up on the idea that the guidelines were subject to change or are despairing about the recent edits that clarified that the use of 'WP' under (B) must avoid uses that could imply the product or service were synonymous with WordPress itself. For similar open source software trademark guidelines and as a useful point of comparison, I think commentators should take a look at Red Hat's public guidelines, which explicitly remind users that guidelines like these can be changed: https://www.redhat.com/en/about/trademark-guidelines-and-pol...
Other commentators are focusing on the length WP Engine had 'WP' in their name. With use since 2010, some have implied that a statute of limitations has passed but the Lanham Act has no such time limit. These commentators don't seem to be considering Automattic's confusion claim. WP Engine has claimed in their materials that they are "The most trusted WordPress platform" and "The Most Trusted WordPress Tech Company". 'Trusted' can be read with the meaning 'seen as trustworthy' rather than the meaning 'utilized' which could be found to be creating confusion. The most [seen as trustworthy] platform would presumably be the project itself (in an expansive understanding of 'platform' that a non-technical user might perceive). If CNET started calling itself "The Most Trusted Firefox Source" I would expect The Mozilla Foundation to ask them to stop. Many commentators appear to be suggesting there should be no enforcement of the WordPress mark, which seems an unusual position, or otherwise seem to take issue with Automattic's original trademark registration in the first place.
Regardless, if WP Engine's uses of the marks exceeded rationales (A) and (B), they needed a license. This is what Matt was seeking, even allowing such a license to be paid in kind. At this point, a court will likely decide if their use exceeded (A) and (B). Calling for Matt to have a role change is one thing but to likely libel Matt with the term extortion, a criminal offense, especially after only moments before admitting "maybe there's validity there" (regarding infringement of Automattic's WooCommerce mark) is absolutely reckless and it's disappointing to see this unserious blog post promoted here. To see uncareful defamation coming from someone who made their living for many years off the software their target of ire created is especially bleak.
I don't think people using the word extortion understand how it is defined in a legal sense and the gravity of the criminality. The word extortion as people use it could be replaced with 'threat' or 'ultimatum', with some sentiment of unethicality or unfairness added back in. Legally, it may be fine for Matt to make ultimatums: "contribute in one of the ways I demand, or my free WordPress.org API that I provide is no longer accesible to you", but as a community steward, it seems unfair to the many users of WPE who were not given that ultimatum with any notice (initially), or enough notice after the "reprieve" (Oct 1 still isn't enough notice.)
The only argument of Matt's I find compelling is that WPE's plan names look like a potential misuse of the WordPress mark. If I was WPE, that would be the only thing I would be worried about, and consider changing (though to do it right now might look like an admission of guilt.) If I was a judge, I would consider slapping WPE's wrist on that point, and considering WPE at most 1% at fault in this entire debacle based on facts available. I don't find the overall trademark confusion argument compelling (especially in light of WordPress.org vs WordPress.com confusion, and WordPress.org as Foundation vs WordPress.org as Matt the CEO of a competitor to WPE confusion), though if Matt wants me to believe his own mom is clueless, I will let him have that point.
After fault finding regarding acts of harm is done, then I'd be willing to consider which companies, including WPE, are leeching in a way that makes them not healthy members of the community, but only after all this is sorted out.
Putting aside all legal arguments, I agree with the directionality of Josh Collinsworth's main point regarding the health of the ecosystem. To put in my own words: Matt's behavior with banning a host's customers from security and feature plugin updates from WordPress.org without sufficient warning (or clear enough reason) has damaged trust in a core single point of failure in the WordPress ecosystem -- I see no excuse for this -- and it is important for the ecosystem to restore this trust as soon as possible.
It's an unacceptable situation to begin with, that something that powers 43% of all sites on the Internet can have security updates degraded on the whim of one individual, no matter how much he contributed to the software in the past.
The most direct way to repair trust would seem to be at the very least to put WordPress.org's update server in the ownership and operation of someone else, preferably a functioning board who was bound to serve the community/ecosystem in a way that included minimizing ecosystem disrupting events like this one, and who established transparent guidelines on what sort of behavior can get a company banned from using these servers (and few mention they are also banned from future conferences). That this event came without warning to many users seems outrageous.
Another thing Josh has right: I and virtually all people hate, to a high degree, greedy ownership of corporations that intentionally lets quality rot as pricing is jacked up and money is squeezed out, so it is very remarkable that so many people think the more critical infraction to the community here is what Matt has done. This isn't about the greedy private equity firm or trademarks right now. It's about a bigger and more urgent problem. We have plenty of time to get back to corporate greed after the current emergency is resolved.
It's rich coming from people demanding a high standard for Matt but not for the WPEngine people.
In the end all of it will get "solved" because there's way too much money in this to go any other way.
As Danny Glover famously said: "I'm too old for this shit"
If you are completely fine with WPEngine's commercial practices, trademark violations in their marketing materials ( like it or not ) and moral OK for them not picking up part of the bill of what they consume ( talking about infra resources, not even talking about code ), then.. why the f** are you so bothered by an unhinged rant from some guy? It's GPL after all.. Don't you see the irony? or you just want to see it because Matt is kind of an unlikable dbag? Is that the level of depth we are at when cheerleading for this stuff?
I don't have a strong opinion on WP Engine's behavior, because I'm not convinced by Matt's arguments. I do have an opinion on Matt's behavior though. I think it's unhinged.
Feel free to respond but I'm done with this conversation, given how unpleasant I feel it's going to be given the incredibly uncharitable tone in your response. I recommend taking a walk or something.
The track record of "modern" would suggest Wordpress is the second coming of Jesus, so no thanks. Wordpress is fine compared to "modern" software.
Because for those of us that are not, WordPress is a pretty easy and pretty capable way to self host something. Without it, lots more stuff would be centralized with Big Tech.
*Static Site Generator
They are not web programmers maybe not even in devops. So It is easier to just buy basic shared hosting wit button 'install wordpress' in hosting-admin.
Statically generated site would be better (especially for readers of the site) but they still need some CMS.
I mean, I liked Drupal, still do, but the business for custom Drupal sites dried up and moved onto WordPress with (insert builder of choice here). Teaching anything on Drupal was like pulling teeth, even in the D7 and D8+ eras. And I'm not aware of any demand for Backdrop / Concrete5 / whatever sites. WordPress even ate up whatever demand there was for Magento (good riddance IMO).
Everyone moved to WordPress because it's easy to teach clients on, the dev costs are reasonable, and there's a really good plugin ecosystem to counter the platform's faults. You can absolutely build unique sites on WordPress and lock them down too.
If WordPress dies, everyone moves to SquareSpace (which is proprietary) or socials (in other words, doesn't have a web presence).
The community was significantly smaller, but many of the plugins that existed were very well maintained, there was a small but healthy set of developers with paid plugins.
I don't want anything to do with that industry anymore, whenever I want to put up a little site I just use a static site generator (hugo). I think there is an interesting potential market for a wp admin like UI that could be used to create hugo posts/etc and manage the theming configuration. Then you click publish, it fires off a hugo container that generates the static site and updates the host... maybe such a thing exists.
There's not really any new information here, nor does the article offer some unique third-party take that hadn't been explored before. It's a lot of armchair psychology, third-hand anecdotes, and unfounded sweeping generalisations. TMZ: Tech Bros.
In fact good leadership demands high amounts of empathy, sensitivity and emotional intelligence.
Either way he is not demonstrating those qualities now.
Then Wordpress will be fine.
In general, anyone who doesn't wake up to E=T/A! will go extinct.
Copyrights are for cons. Patents are for parasites. Licenses are for losers.
You can only ignore nature for so long.
Empirically we have been seeing this for a while (look at the dominance of open source programming languages, for example. Even Microsoft open sourced C# b/c they saw it was dead otherwise), but now we have a simple undeniable formula which explains this which is roughly E = T/A! [0]
You can keep your head in the sand and pretend that things aren't going to change, but the bottom line is if you stick to (c) and patents you retard your own development and will be driven to extinction by your competitors.
by all means this guy is not the best one to call removal of Matt. this also reminds me those VC that got rid of the founders because founders have some flaws, and VC forgot that,without those flawed founders there will be nothing to start with.
Which is a bit of a contrast to what Matt is doing.
> We don’t need to dredge up a bunch of old and buried stuff that isn’t really important anyway, but suffice to say: I really don’t have any reason to be a WP Engine cheerleader. Most of the people I knew there have left, and I’ve watched from the sidelines as the company has implemented a bunch of scummy policies and shady sales tactics to squeeze money from their customers and make it harder to leave.
If this isn't good enough for you then you're not being honest, you are just desperately looking for any excuse to defend Mullenweg.
The omission of that suggests that he does have a financial stake.
Contrast that with Matt's original tirade where he didn't mention the licensing deal he put in front of WP Engine that they turned down.
I don't understand what it means for those principles to be in conflict and I'm not sure that I would agree, upon clarification, that one is being put above the other or that the nature of the relationship between them is such that you choose between them with mutual exclusivity.
Also note that the author doesn’t disclaim any financial stake in the company he used to work for, WP Engine, after his company was acquired. He merely claims that he isn’t a “fan of either party”, so we should value his opinion and trust that it is impartial.
As for myself, I’ve never used WordPress or any CMS, I’m a lowly embedded software engineer. If Matt, the progenitor and steward of one of the most successful open source products in the world, asserts that an entity in the ecosystem is a leech, I’m inclined to believe him.
By that definition, TinyMCE should be able to disable all textareas in Wordpress, since the product has used it freely for years without contributing anything.
And Lodash should be able to disable TinyMCE.
And QUnit should be able to disable Lodash.
It's open source. Should every Linux user be -required- to contribute? I'd bet the OS quality would degrade if that were so.
I am left with the question: why, after 13 years of WP Engine doing the exact same thing, is Matt now willing to burn down the house?
Matt mentioned it's costing them millions per year to provide them with automatic updates and other services they provide.
And he also mentioned that they can host these services on their own, since the code is GPL2. They don't do this because they don't want to pay these costs themselves.
if WP Engine contributed to source, would they suddenly be allowed to rack up API and CDN bills?
This wasn't an issue of "it's abusive traffic"—and how could it be, being the code that Automattic wrote!—it's an issue of Matt Mullenweg throwing a temper tantrum and turning unsuspecting WordPress users into collateral damage. There's no way to operate these features without WordPress infrastructure (you might even argue that it's not feasible, as it's never been done before by someone other than Automattic!). WordPress isn't just "not providing updates", they're actively blocking these users for purely political reasons. The users have been turned into cannon fodder.
Matt might well be throwing a temper tantrum, and almost certainly causing brand damage, and the result of the conflict might be actual harm to end users. BUT WP Engine doesn't get to hide behind the limits of their obligations under the open source licenses and then shift the blame they should rightfully be taking onto Matt because of his temper tantrum. Real users are not getting security updates or features they expected because the company / vendor they are buying their product from did not do due diligence to secure their supply chain. Matt could decide tomorrow to stop releasing new WP versions, or change the license (modulo CLA stuff). It's not like sudden, fundamental changes to the upstream licensing / sourcing hasn't been a constant source of headlines and conflicts for the last few years now. CentOS, Redis, HashiCorp, Akka, CockroachDB, and many more projects have fundamentally "altered the deal" and downstream customers relying on them have been caught in the crossfire. Heck, even the GPL2 vs GPL3 debate is an example of this. Are all the projects that switched to GPL3 for anti-TiVoization clauses guilty of throwing temper tantrums? Plenty of real world users were harmed by moves to GPL3, for example, Bash on macOS is stuck at 3.2 and users were forced to migrate to zsh over this move.
> There's no way to operate these features without WordPress infrastructure
Is WordPress not open source? What stops WPEngine from doing it themselves, they have the source. If its too hard, well that might explain then why their upstream vendor wants some compensation for the work. We (rightfully) criticize commercial companies for not putting resources into the huge numbers of open source projects and labor that underpins their very existence. Well this is another example of that. If an upstream source is so critical to your business that its loss would cripple you or your customers... maybe consider spending some money on securing and retaining access to that source.
It's not WPE's supply chain, it's the end users' supply chain. There's no way they could have seen this coming. Targeting WPE was essentially arbitrary. Users are affected because WPE was cut off, not because they did anything wrong.
> BUT WP Engine doesn't get to hide behind the limits of their obligations under the open source licenses
I'm curious to know what you think they should have done, because other then just heap money on a literal direct competitor, I can't imagine what they could have done.
> Is WordPress not open source? What stops WPEngine from doing it themselves, they have the source.
How are they supposed to have a copy of all the updates if they're blocked? This is such a nonsense suggestion. Of course they could run the servers, but those are empty servers with no data.
> If an upstream source is so critical to your business that its loss would cripple you or your customers... maybe consider spending some money on securing and retaining access to that source.
You're only just defending Automattic's literally extortion tactics. Should I as a user be worried that Linode or Hetzner will be blocked next because they aren't paying a tithe to WordPress?
I suppose not pissing off their single and sole supplier of the product they're reselling to their customers might have been a smart move. If you buy your product from your competition, you probably need to stay on their good side. Maybe not re-selling a product when their continued access to the product was controlled by a competitor might also have been a good idea.
> Of course they could run the servers, but those are empty servers with no data.
Do they not have the source? Probably time to start hiring some developers and make their own patches for security issues in the product they're selling. No warranty express or implied is exactly that. They get the software, they get the source. Everything else is a bonus. Especially if the defense of their conduct is that there's no obligation for them to have done anything more than the license required of them.
> Should I as a user be worried that Linode or Hetzner will be blocked next because they aren't paying a tithe to WordPress?
Yes, you probably should be. Any time you're reliant on a single source of failure for a critical component of your business you should be worried about it. Sometimes you accept the risk and nothing happens. And sometimes you accept the risk and something does happen and you learn why redundancy is important.
A single hosted plugin repository is a huge multiplier towards ecosystem growth, but WordPress always had the option of distributing the load by asking others to set up mirrors, and offering a selection of mirrors. Y'know, redundancy. They've never done so.
There's also no option in the WordPress core to easily point towards a different repository URL.
Maybe this whole debacle would lead to slightly more decentralisation of WordPress, which might be a good thing for the long-term health of the project and community.
2. All those products have no marginal cost for users, WordPress.org does.
3. Just because bad behavior has been tolerated for a time doesn’t mean it must be tolerated forever.
No, not every user. Only entities that make millions of $$$ directly with that free software. They should be required to contribute!
Either donate directly or contribute hours proportional to your dependency on the project.
It would hardly be shocking if he had some stock or whatever, given how prevalent that is for tech workers' comp.
However, if it were me, and I did have a financial stake in WPE, I would not/could not write either of these sentences from TFA under my personal view of honesty:
I really don’t have any reason to be a WP Engine cheerleader.
I can assure you it’s not me defending my old company just because I used to work for them. I’ve got literally no reason to do that.
I doubt it, and it would be wrong to do so.
If he didn’t have a financial stake, he would have listed it in his myriad reasons to trust him.
>I’ve watched from the sidelines as the company has implemented a bunch of scummy policies and shady sales tactics to squeeze money from their customers and make it harder to leave.
And
>On most days, if you wanted to have a conversation about how much WP Engine sucks, frankly, I’d be a happy participant.
More to the point, he lays out a ton of specifics about how Matt acted like a Grade A Asshat. If you have any issue with those specifics, you can and should state your objections.
But your comment here is just nebulous BS. Saying "This reads like part of the smear campaign predicted by Matt in his interview with Michael Paulson" sounds exactly to me like when Elizabeth Holmes gave her now infamous retort "first they think you're crazy, then they fight you, and then all of a sudden you change the world". Both are equally vacuous statements that don't address the specific criticisms put forth.
1. The author claims dozens of other companies behave similarly and claims that Matt has not taken any action against them. However, the author makes no claim of what level of contribution to WordPress, cost to Wordpress.org, or any contractual agreements those companies may have with WordPress entities. Multiple companies do pay for trademark licenses. Scale is also an important factor here. Estimates are in the hundreds of millions of revenue for WP Engine. They are one of the largest companies in the ecosystem, of course they should be contributing more than smaller players.
2. The author claims that Matt attempted “extortion” and refused to give WP Engine more time to address his demands. It does seem true that Matt refused to give them more time. However, Matt claims this conversation has been going on for more than a year. A deadline seems appropriate if your counterparty keeps delaying.
3. The author claims that trademark confusion between WordPress and WP Engine is an unfounded concern, citing confusion Shopify and Spotify. This is ludicrous on its face, those companies serve completely different market needs, compared to the WP Engine literally offering the product produced by the trademark holder. The author claims that WordPress.com and WordPress.org is confusing the trademark, but doesn’t state whether WordPress.com has a license to use the trademark.
4. The author claims that Matt’s dissatisfaction with WP Engine’s contribution is unreasonable because there aren’t terms and conditions or a contract. This is missing the point entirely. The point is that good members of the community shouldn’t need to be forced to contribute. If they want to play by the letter of the law, Matt isn’t obligated to provide the free services that their business relies on, just as they aren’t obligated to give back. It cuts both ways, and if they won’t operate in good faith, it is self destructive to continue to enable them.
I’m out of energy to continue, so I’ll stop here.
What would "seem appropriate" would be some form of terms and conditions, or contract, or legal authority that would warrant any of this business about imposing any deadlines or demands of any kind whatsoever, in the first instance. The time isn't Matts to give or not give to begin with.
>The point is that good members of the community shouldn’t need to be forced to contribute.
I think the author was at pains to emphasize through the beginning middle and end of the article that there was such a thing as a right way to make this case. And the problem is weaponizing certain levers at WordPress in ways that raise all kinds of conflict of interest issues, have the potential to cause all kinds of collateral damage, and undermining credibility and integrity of WordPress as a long-term project.
The ultimatum Matt made in the texts highlighted by WP Engine appears short, but it seems unlikely this was the first time Matt brought up these issues.
If Matt can pull the rug on one host's customers without notice, he can do it again. He has been on streams saying no other host is in the doghouse with Matt, but a week ago almost nobody knew WPE was on thin ice.
If Matt didn't do the reasonable thing to warn WPE customers, what other unreasonable things is he capable of doing in the future?
The "reprieve" of a new Oct 1 deadline is still far from reasonable in my opinion to the point that it is further infuriating that he is using it to virtue signal, though it is at least a tiny start of an implicit acknowledgement that he screwed up. But it's a matter of rebuilding trust in the ecosystem now, and I think Matt is still digging a hole, and this can't be fixed until he apologizes, and the governance of the WordPress.org update server is clarified (best case: out of Matt's hands), or somebody more neutral creates a competing update server, fracturing the ecosystem.