We are _actively_ making contingency plans. But our best estimate at this stage is that WPEngine will provide a suitable way to keep all our WPEngine sites running at least in the short and medium term, but we are also making disaster plans in case this all goes, as Matt intends, "nuclear".
Matt keeps talking about how he's doing this "for the WordPress Community", but as I commented elsewhere:
So far as I can tell, when Matt talks about "the WordPress Community", he means:
- Matt
- the people who didn't quit Automattic last week
- _maybe_ the WP core developers who don't work at Automattic, so long as they keep their criticisms to themselves
And the community of people who _use_ WordPress to run their websites, and the people who help them to do that, and the 3rd party plugin and theme developers who make WP work for so many different kinds of websites - can all go and get fucked.I work at a hosting company and we have received zero questions, and we have a fair larger number of clients who sites are built on wordpress. In terms of going nuclear, anything regarding trademark will have zero impact on our clients.
> In terms of going nuclear, anything regarding trademark will have zero impact on our clients.
Is that true if Matt/Automattic win against WPEngine, and he starts using that as precident and starts demanding 8% of revenue as his standard shakedown on anybody who's used the "WordPress" trademark to generate revenue?
Is that client of yours a web developing company that focus on wordpress in their marketing?
They have a quite technical marketing team (well, two people) who run the WP site, which they're quite aware of how often plugin and partner theme upgrades show up. The call was basically "So what's going to happen with WordPress and plugins? Are we going to be able to rely on updates and future security for the website?" She wasn't worried that they were gonna get caught up in a trademark problem, but that the trademark "war" would kill off WordPress core development, and/or the future development and bug/security fixes of the plugins they rely on. A reasonably valid fear, and one that I certainly don't dismiss out of hand.
The WordPress code is available to WPEngine. How are Mullenweg's actions damaging them?
WP Engine is a prominent hosting provider for WordPress, who also contribute several very popular plugins.
Automattic have sued WP Engine. Automattic have blocked WP Engine from updating any of their plugins, or anything else on wordpress.org. A vulnerability was found in a WP Engine plugin, and Automattic have taken it over (but are not doing any maintenance). Automattic's CEO went on a number of unhinged rants here and elsewhere.
But everyone is still able to publish their blogs, on both WordPress and WPEngine?
And both WordPress and WPEngine are able to fork each other's code and run separate platforms?
So long term fragmentation is the main danger?
Am I completely off the mark?
Maybe that's not what you meant. I have no dog in this fight. Just telling you why someone would assume you are expressing an opinion.