Earlier quoted context omitted.
And what is more sad is that it really appears that the WordPress figurehead is to blame. Matt has made so many unforced errors in the last month, in addition to revealing, one way or another, that he basically considers WordPress, the .org, the .com, the Foundation, and Automattic, all to be synonymous, which is news to a significant portion of the community, let alone to the incorporation and other founding filings…
He's completely unhinged. The threats that he made that are outlined in this document... how is this NOT extortion? Any lawyers around?
Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
91–100 of 717 posts
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#92Howdy, 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…
That's not what page 35 says at all. Check out page 36: > 92. Mullenweg’s premise was false, as WPE’s CEO had never interviewed with or negotiated a job offer with Automattic. To the contrary, back in 2022 Automattic had asked if she would be interested in running wordpress.com, but she politely declined. (edit: I have no idea who is right, but it's just not correct to read page 35 as saying that)
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#93Howdy, 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…
Your response to this complaint is going to look very interesting. Also, a note for the audience: Quinn Emanuel is one of the premier (and most expensive) litigation firms in the US. Partners in their litigation department run $2000/hour or more. Associates cost almost $1000/hour. WPEngine apparently has deep pockets.
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#94Earlier 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.
https://plugins.trac.wordpress.org/browser/woocommerce-gatew...
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#95Earlier quoted context omitted.
That's not what page 35 says at all. Check out page 36: > 92. Mullenweg’s premise was false, as WPE’s CEO had never interviewed with or negotiated a job offer with Automattic. To the contrary, back in 2022 Automattic had asked if she would be interested in running wordpress.com, but she politely declined. (edit: I have no idea who is right, but it's just not correct to read page 35 as saying that)
She was interviewing November 2023 to January 2024. She declined the WordPress.org role on January 26, 2024. I even invited her to my 40th birthday on Jan 11, another text message she decided not to share.
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#96Howdy, 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…
"she wanted to be the Executive Director of WordPress.org for Automattic" But you own and run and finance WordPress.org personally, as you've revealed and talked about numerous times in the last few weeks. I don't follow, how can Heather apply for a job with Automattic to be the Executive Director of a website you personally own?
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#97I 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.
While you are telling lies about trademark violations and extorting money specifically from WPEngine and have publicly admitted you're not doing that to anyone else that provides Wordpress hosting? And you've used terms like "war" and "nuclear option" when threatening the lies you subsequently told?
And somehow you still think _you're_ the good guy here?
:boggle:
Just resign. Make the WordPress Foundation into everything you've pretended it is over the years, including rightful and permanent owner of the trademarks and .org domain, and complete seperate from you personally and Automattic and it's related businesses. _Maybe_ that'll save WordPress. Maybe...
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#98Howdy, 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…
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#99I 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.
The onus is on you now to respond. The best venue for that is the courts, not online forums and social media (that was 2 weeks ago).
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#100Earlier quoted context omitted.
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…
One of the two entities completely controls the plugin ecosystem and wielded that control against the other entity (the largest WordPress host except, possibly, Automattic itself) to block them and all of their customers out of the ecosystem over this dispute. That's why this matters to average developers. WordPress is the plugin ecosystem, and messing around with it does as much damage to the WordPress ecosystem as…