Live data from Hacker News

Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

wpengine.com

101–110 of 717 posts

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#101

Earlier quoted context omitted.

What would you like me to answer? I haven't doxxed any private texts from other parties like they have. I've only been releasing things I've said or sent.

Sure, it was a few text messages at the end of a months-long negotiation about a licensing deal. We posted the timeline and the final term sheet here: https://automattic.com/2024/10/01/wpe-terms/ WP Engine's business is built on violating the WordPress and WooCommerce trademarks, 8% is typical for a franchise fee. They confuse customers in the marketplace who think they're official WordPress. If you watch this stream…

If you offer someone a contract, they stall for a few months, and you show up at their house with gasoline and a match and threaten to burn their house down if they don't agree to sign the contract, you're guilty of extortion.

The context you need to share isn't that there exists a document that you wanted to sign and that they knew existed before you made the threats, the context you need to share (Edit: in court, you should really shut up here for your own good) is context that makes those texts not look like threats to drag their name through the mud in a massive smear campaign if they didn't agree to sign.

No one here is disputing that you might have been in the right until September. It's your actions in September that you need to account for.

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#102

Earlier quoted context omitted.

"The agreement wasn't about their license to the code," Maybe you misread it (or miswrote it i guess)? it says: "WP Engine will cease and desist from forking or modifying any of Automattic’s, WooCommerce’s, or its affiliates' software (including, but not limited to plugins and extensions) ..." It could not more plainly say that they cannot fork or modify software .

"The agreement wasn't about their license to the [GPL] code," And "WP Engine will cease and desist from forking or modifying [non GPL code]" You are misreading it.

1. Matt just claimed it wasn't about software at all. So we've now moved on to saying "well it's about code, but not GPL code".

Progress, i guess?

2. The agreement does not limit it to non-GPL code in any way, so i'm really not sure where you are getting that from. The plain terms cover all of automattic (et al) software, which includes the stuff that has GPL code in it.

The normal way such an agreement would be written to cover only non-GPL pieces would be to say it does not attempt to modify or change rights you get elsewhere, blah blah blah. It includes no such clause.

If you've got meaningful parol evidence that it was meant to cover only non-GPL code, great, let's see it. (since the agreement is both badly written and not fully integrated, it would be valid to do so).

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#104

I hope Matt can supply his legal team with conversations that would somehow justify his behaviour. From my (incomplete) reading of the complaint, he (Matt) does indeed look very "petulant". It's almost like he's intentionally self-destructing, which is why I hope for his sake that he has more tangible evidence to share, especially after reading section 201.

Yes this is part of their smear campaign, just like their last C&D. They're cherry-picking stuff to try and make me look bad, while not addressing the core issue of their trademark violations. They want me to stop telling their customers about their bad behavior.

Man... You are still talking on the internet publicly, obviously without any lawyer checking out what you say before you post comments. You will inevitably end up posting a lot of things that can make you look bad or sink the case for your side. Just stop talking about this anywhere online and offline. Let the lawyers talk.

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#105

Earlier quoted context omitted.

What would you like me to answer? I haven't doxxed any private texts from other parties like they have. I've only been releasing things I've said or sent.

Sure, it was a few text messages at the end of a months-long negotiation about a licensing deal. We posted the timeline and the final term sheet here: https://automattic.com/2024/10/01/wpe-terms/ WP Engine's business is built on violating the WordPress and WooCommerce trademarks, 8% is typical for a franchise fee. They confuse customers in the marketplace who think they're official WordPress. If you watch this stream…

> 8% is typical for a franchise fee

I see many WordPress hosts use these trademarks in the same way WP Engine does.

How many of them are paying this typical 8% of monthly revenue fee?

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#106

Howdy, Matthew Charles Mullenweg from the lawsuit here. One thing I'm surprised they disclosed is on page 35 that Heather Brunner at WP Engine was interviewing for a job at Automattic. That's why we were spending so much time together 1:1 without her team there in the meetings I posted here: https://automattic.com/2024/10/01/wpe-terms/ They lied that it was to run WordPress.com, though, she wanted to be the Executive…

Heather Brunner is an amazing person and leader. I know because I used to work with her. That's it. That's the comment.

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#107

Howdy, Matthew Charles Mullenweg from the lawsuit here. One thing I'm surprised they disclosed is on page 35 that Heather Brunner at WP Engine was interviewing for a job at Automattic. That's why we were spending so much time together 1:1 without her team there in the meetings I posted here: https://automattic.com/2024/10/01/wpe-terms/ They lied that it was to run WordPress.com, though, she wanted to be the Executive…

Since you're trying to get WP Engine to pay for "WordPress" trademark, by contributing back to open-source, because you feel they should, since it made them rich, I was wondering how many open-source projects did Automattic contribute to financially? Aside from WordPress, I'm sure you stand on the shoulders of giants such as Linux, nginx, MySQL, JavaScript libraries (or maybe you should call it ECMAScript, because yo…

They're listed as a sponsor on the PHP Foundation website.

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#108
post #76

Is it just me who took a double take at the very first name? WPE called the heavy cavalry -- Rachel Kassabian from Quinn Emanuel? oh boy. Remember Perfect 10, Inc. v. Amazon.com, Inc which found thumbnail versions of copyrighted images for search engine purposes is fair use? That was originally against Google and she was Google's lead counsel.

I noticed her name in the original C&D, too (amateur tech legal nerd).

For those curious:

https://www.quinnemanuel.com/attorneys/kassabian-rachel-herr...

She's done a lot of notable copyright work for Google, Yandex, Vimeo, Cloudflare and (ironically) Tumblr - amongst others.

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#109

Howdy, Matthew Charles Mullenweg from the lawsuit here. One thing I'm surprised they disclosed is on page 35 that Heather Brunner at WP Engine was interviewing for a job at Automattic. That's why we were spending so much time together 1:1 without her team there in the meetings I posted here: https://automattic.com/2024/10/01/wpe-terms/ They lied that it was to run WordPress.com, though, she wanted to be the Executive…

I am stunned that you're still posting publicly and aggressively about all of this. How have your lawyers okayed any of this?

Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]

#110
post #26
post #10

What's sad here is that this dispute isn't likely to make Wordpress any better, but rather send money to lawyers and reduce enthusiasm for the OSS project.

I’m an arm length removed from all this drama having not used Wordpress in a while, but to be honest this opinion feels overblown. To an outsider, it just looks like some legal issue between two entities irrelevant to my concerns on whether I’d use or contribute to Wordpress in the future. Something that happens between corporations all the time My guess is there will be some settlement, one party will walk away with…

I mean sure if you want to rely on a tool where this guy will disable chunks of it because he's had a hissy fit, I guess it "won't affect you".
Post reply on HN