3 ms·

They won't need to fork WP itself (though they're totally free to do that, WP started as a fork after all), but it sounds like they may need to quickly focus on

by err4nt 2y ago

They won't need to fork WP itself (though they're totally free to do that, WP started as a fork after all), but it sounds like they may need to quickly focus on creating their own plugin and theme marketplaces, and other services that WordPress.org provided to WordPress CMS users but is not denying to WPEngine. Let this be a lesson to all of us - if you rely on a service provided by another organization external to your organization, get an SLA! Get a contract that guarantees you the provision of services you depend on.

ValentineC 2y ago
> if you rely on a service provided by another organization external to your organization, get an SLA! Get a contract that guarantees you the provision of services you depend on. Getting "takers" to pay for SLAs/licences is pretty much what Automattic or whoever's behind WordPress dot org wants.
- lsaferite 2y ago
  The whole divergence of this kerfuffle into the resource usage of WPE hosted WP sites against the WP.org site is a distraction and an ex post facto justification. Matt got twisted when WPE wouldn't pay Automatic and is lashing out. If he wanted them to cover costs for WP.org, that would have been a totally different conversation. Even crying foul over WP.org costs is disingenuous though. It's not WPE consuming the resources, it's the sites they host for customers. It'd be like Matt demanding 8% of AWS revenue because so many sites are hosted by them and accessing WP.org resources. Simply collecting the hosting of multiple WP sites under one provider should in no way obligated the provider directly. Either it's a freely accessable resource for WP sites or it's not. It should not be subject to the whims of a single person and used as a tool in their personal crusade. Given that it's clear that WP.org is not actually a freely available resource, it's imperative that the WP codebase be adjusted to not use that resource anymore. As I've said in most of my posts on this, I'm not involved in the WP world and have no ties to any party to this debacle.

by err4nt 2y ago

ValentineC 2y ago

> if you rely on a service provided by another organization external to your organization, get an SLA! Get a contract that guarantees you the provision of services you depend on. Getting "takers" to pay for SLAs/licences is pretty much what Automattic or whoever's behind WordPress dot org wants.

lsaferite 2y ago
The whole divergence of this kerfuffle into the resource usage of WPE hosted WP sites against the WP.org site is a distraction and an ex post facto justification. Matt got twisted when WPE wouldn't pay Automatic and is lashing out. If he wanted them to cover costs for WP.org, that would have been a totally different conversation. Even crying foul over WP.org costs is disingenuous though. It's not WPE consuming the resources, it's the sites they host for customers. It'd be like Matt demanding 8% of AWS revenue because so many sites are hosted by them and accessing WP.org resources. Simply collecting the hosting of multiple WP sites under one provider should in no way obligated the provider directly. Either it's a freely accessable resource for WP sites or it's not. It should not be subject to the whims of a single person and used as a tool in their personal crusade. Given that it's clear that WP.org is not actually a freely available resource, it's imperative that the WP codebase be adjusted to not use that resource anymore. As I've said in most of my posts on this, I'm not involved in the WP world and have no ties to any party to this debacle.