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…
Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
121–130 of 717 posts
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#122Earlier quoted context omitted.
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]
#123Earlier 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…
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#124Howdy, 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]
#125Earlier quoted context omitted.
Why you don't share it? You said there's much more emails and messages, but you never shared any. Why not?
Why doesn't she share messages that prove she declined a WordPress.com job in 2022? You're holding me to a different standard. I'm here, I'm talking to journalists. They're not.
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#126Makes Matt look like just another guy with money throwing a tantrum because he didn’t get what he demanded. Sad because many thought highly of him before he went off the reservation.
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#127Earlier 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…
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#128Is 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.
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#129Howdy, 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.
- Page 12: "wordrpess.org"
- Page 17: "fundamental principal"
Re: Filed: WP Engine Inc. v Automattic Inc. and Matthew Charles Mullenweg [pdf]
#130Earlier quoted context omitted.
[flagged]
Thanks, I carry a co2 and carbon monoxide monitor. Co2 where I'm at is 572. I do own a place in Montana, and I meditate several times a day. I have not threatened to take down WordPress.org. WPE's preservation requests do complicate things, legally, though, for the Slack and forums that W.org offers. Both Cloudflare and Fastly have reached out offering CDN services to W.org, which we're considering. Cloudflare also s…
If you're "right" and "on the side of good and freedom", what are you worried about in Slack/forums/whatever?
Because everything made public so far in their filing is pretty fucking bad (for you), I can only assume that discovery is gonna reveal some even worse behaviour on your part - or you'd have responded in public with some of that instead of whining about "preservation requests complicating thing"...