5 ms·
This is a pretty one-sided summary of the situation and, despite citing the Theo Browne interview, leaves out from it that WPE and WordPress and Automattic have
by tptacek 2y ago
This is a pretty one-sided summary of the situation and, despite citing the Theo Browne interview, leaves out from it that WPE and WordPress and Automattic have apparently been in protracted negotiations about this for over a year. Users are understandably shocked by this outcome, but it seems implausible to claim that WPE was.
I think it's also useful to note that Mullenweg wasn't demanding 8% of WPE's revenue, but rather an allocation of WPE revenue to WordPress ecosystem development (by staff members on WPE's own team), with the revenue to Automattic (or whoever, I forget) as an in-kind payment option.† That is a much more reasonable-sounding ask than simply forking over cash to Mullenweg's own business.
I'm not following this closely enough to vouch for the way Mullenweg is handling any of this (though: at this point I assume/hope he has counsel reviewing what he's saying!) but it would be weird to me at this point to see WPE cast as the "good guys" here. This seems like another one of those "it's just a bunch of guys" scenarios.
† This is according to Mullenweg, of course, but he had Theo Browne reading emails to WPE off his laptop during the interview to back the claim up.
- aimazon 2y ago"Negotiation" invokes visions of term sheets and boardrooms but what Matt actually meant by "negotiation" (as revealed in the interview) was emails in which he expressed displeasure at the lack of contribution from WP Engine, and only in the days before WordCamp did any sort of terms arrive at the table (the 8% demand). Matt has acknowledged he escalated things in the space of days, not years. The emails read out are birthday party invites, not term sheets. I agree that WP Engine cannot be characterised as "good guys" given it's a bottom-line driven machine that will chew up and spit out all in its path, and Matt has earned credibility through decades of community-minded WordPress stewardship, but let's not pretend this is some business deal that went sour, it's Matt using every inch of leverage he has to cause WP Engine pain because of his moral objections to the private-equity machine taking money away from his community-minded company. Obviously WP Engine were never going to pay Automattic tens of millions of dollars per year, Matt knows that, we know that, it's a side show. He was just saying things to ruin their day. Just like the millions of dollars per year in costs incurred running WordPress.org that Matt has wheeled out to justify causing WP Engine pain by cutting them off from plugin updates (Cloudflare have offered to host WordPress.org for free; Matt has not accepted the offer).
- tptacek 2y agoAt 14:50 in the video they read a term sheet together. Prior to that, they read aloud an email complaint (not a birthday party invite) from this summer. He claims that they've been meeting in person about this; I don't disbelieve him. For what it's worth: I agree with you about what seems subtextually to be behind this whole thing. But then: if they've been on notice for many months about Mullenweg being upset about their use of the trademarks and lack of participation in the community (confirmed on camera, unless he forged emails), it feels to me like WPE --- a company with an 8-9 figure run rate --- should have been in a position to know what was coming with WordPress.org and how to mitigate that. I'm not casting Mullenweg as a hero; just making a case for it being a JABOG† situation, as I said above. And, of course, that the summary in the story we're reading is pretty one-sided. † gonna make this a thing
- Terretta 2y agoThe trademarks argument seemed overblown, "JABOG" style. The new to me allegation in this is this alleged WPE swap out of WooCommerce Stripe affiliate account: WP Engine had been siphoning “tens of millions” of dollars away from Woo’s revenue share partnership with Stripe into its own coffers. It’s understood WP Engine has been swapping out WooCommerce’s Stripe Connect Account information for its own when a user installs WooCommerce. Ripping out an OSS' revenue model would seem not great. There's a term for use of electronic communication systems to redirect money to oneself. But, not cut and dried, if the source code containing that model is fair game... To your point, this must be a one-sided take as well, since one would have expected an accusation of 8 figure wire fraud to escalate more clearly if it were that simple.
- threeseed 2y agoYou're missing the point that WP Engine forked WooCommerce. It is their version of the project and they are permitted by the terms of the license that WooCommerce agreed to make whatever changes they like. Open source is a double edged sword. You can't leverage the benefits of the community and then deny the community the ability to benefit themselves.
- bawolff 2y ago> I think it's also useful to note that Mullenweg wasn't demanding 8% of WPE's revenue, but rather an allocation of WPE revenue to WordPress ecosystem development (by staff members on WPE's own team), with the revenue to Automattic (or whoever, I forget) as an in-kind payment option.† That is a much more reasonable-sounding ask than simply forking over cash to Mullenweg's own business. I think the question is, in exchange for what? I think the reason that all this is controversial, is it feels a bit like a shake-down. Give us some resources, otherwise, while, that is a nice wordpress business you have there, it would be a shame if something happened to it.
- threeseed 2y ago> it feels a bit like a shake-down It is a shake down. And the problem with negotiating with people like this is that it never stops. There will never be enough contributions and money.
- Terretta 2y ago> the problem ... with people like this is that it never stops. By contrast, this doesn't make WPE look good: WP Engine had been siphoning “tens of millions” of dollars away from Woo’s revenue share partnership with Stripe into its own coffers. It’s understood WP Engine has been swapping out WooCommerce’s Stripe Connect Account information for its own when a user installs WooCommerce. That's the sort of thing that, if a proven problem, could seem less like a shakedown and more like active wire fraud. EDIT: As replies note, GPL. OK, but I realize I grew up thinking if someone gives me software it isn't to rip out their revenue model and replace it with mine, it is for me to do my own value added thing with it. Meaning, the stealth edit might not be wrong, but still seems uncool.
- djbusby 2y agoOr at least misleading the consumer - which is also not cool.
- threeseed 2y agoThat is completely legal and ethical. WooCommerce is an open source, GPL project which allows people to modify the code in any way, including changing Stripe details, provided that they comply with the terms of the license. Licenses are a fundamental part of open source precisely so that in situations like this everyone knows the rules of the game.
- jcranmer 2y agoI think at this point three things are true. The first is that Mullenweg sincerely believes that WPE should be contributing more than it is to the development of WordPress. The second is that they have no legal obligation to do so, which gives Mullenweg very little leverage to force them to do anything. The final thing is that the setup of WordPress and Automattic and Mullenweg's role in both makes any attempts to apply social pressure to achieve his aims at best a case of bad optics and at worst a saunter through a legal minefield with some hexanitrohexaazaisowurtzitane strapped to his back.
- tptacek 2y agoSure, and style points for the Derek Lowe allusion. I see why you think this, and probably agree more than disagree. Three things that have influenced how I look at this: * The revelation that Mullenweg was asking for headcount allocated to the WordPress project, not simply a cash payment. If you get a giant company rolling that is driven entirely off an open source project, it seems very reasonable to me for the open source project to use whatever leverage it has to get you contributing back. * Mullenweg's argument that the norm for projects in "his" predicament to simply relicense to non-open-source terms; this seems incontrovertibly true, and also like it does a lot more damage to an open source community than what Mullenweg is attempting to do, which is to demand that a non-contributing company take his project's name out of their (marketing) mouths, and to stop using public services provided at the project's expense. WPE is in a position to mitigate anything Mullenweg can do here, so it's hard for me to sympathize too much. * I was radicalized on this by working in security products during a time where it felt like dozens of funded startups were just picking up Snort and running with it as their core engine without contributing anything back, including proprietary stuff they built on top of it (and shipped in appliances, avoiding the licensing issues). I keep saying this is a "JABOG" situation, and I do believe that, but I have to remind myself of that to avoid casting one of these parties as the obvious bad guy.
- yjftsjthsd-h 2y ago> Mullenweg's argument that the norm for projects in "his" predicament to simply relicense to non-open-source terms Isn't WordPress using GPL code owned by other people? He doesn't get brownie points for not doing something that's illegal.
- ankleturtle 2y agoHe demanded either 8% of their gross revenue, the equivalent in development time for employees who would be directed by WordPress.org, or some combination thereof. He also demanded auditing of WP Engine by their direct competitor, Automattic. 0. https://automattic.com/wp-content/uploads/2024/09/term-sheet-wp-engine-inc.-automattic-trademark-license_09.19.2024-1.pdf https://automattic.com/wp-content/uploads/2024/09/term-sheet...
- JimDabell 2y ago> for employees who would be directed by WordPress.org And as a reminder, WordPress.org is just Matt Mullenweg. It’s not even the WordPress Foundation, which is headed by him. WordPress.org is literally just him. > > Do you really individually own http://WordPress.org http://WordPress.org? > > Not Automattic? Not a different LLC or something? No employees? No board of directors? > > Just you? > Just me. — https://x.com/grigs/status/1840958978043605361 https://x.com/grigs/status/1840958978043605361 So when Automattic offered WP Engine a term sheet that demanded that they put 8% of their gross monthly revenue towards employees “directed by WordPress.org”, what it’s actually demanding is that WP Engine pay the salaries of developers who would work for the CEO of their direct competitor. Not to mention the fact that salaries are not the only cost incurred when employing somebody, so greater than 8% of their gross monthly revenue would be spent on Mullenweg’s flying monkeys.
- FireBeyond 2y agoI think Matt has gotten far too used to using wp.org, wp.com, Automattic, and the Foundation effectively interchangeably for years.
- FireBeyond 2y ago> the equivalent in development time for employees who would be directed by WordPress.org Uhh, as Matt has stated, WordPress.org is him and him alone, a gift to the WordPress Foundation. So Matt has demanded that WPE give this to WP.org, which belongs to him...