WordPress blocks a large hoster, leaving users without updates.
The scandal around WordPress.org escalated - the management of the resource blocked the hosting provider WP Engine from accessing its resources. This decision is due to disagreements between WordPress co-founder and Automattic CEO Matt Mullenweg and WP Engine.
Mullenweg stated that WP Engine will not have access to the platform's resources, including themes and plugins, until legal issues are resolved. He noted that WP Engine aims to take control of the WordPress user experience by managing authorization systems, server updates, and directories of plugins, themes, blocks, and other resources.
Mullenweg emphasized that WP Engine can offer its customers its redesigned version of the WordPress code under the GPL license and provide its services. But WP Engine servers will no longer be able to connect to WordPress resources for free. As a result of the ban, WP Engine users are deprived of the ability to install plugins and update themes through WordPress.org.
Many WordPress developers and supporters have expressed concerns that such a restriction could prevent WP Engine users from receiving security updates, potentially leaving sites vulnerable. In turn, WP Engine acknowledged the problem and announced that it was working on a solution, noting that the ban does not affect the performance, reliability or security of sites, as well as the ability to make changes to code or content.
It's important to understand that WordPress powers nearly 40% of the websites on the internet through various hosting providers, including Automattic and WP Engine. Users can also take an open-source project and launch websites on their own, but many prefer to use plug-and-play solutions.
The standoff between WP Engine and Automattic began last week when Mullenweg publicly accused WP Engine of profiteering and called the company a "WordPress cancer". According to Mullenweg, the company doesn't contribute enough to the WordPress community, even though both it and Automattic make about half a billion dollars annually.
Amid the allegations, WP Engine sent a letter to Mullenweg and Automattic demanding that they stop spreading such claims. The letter alleges that Automattic threatened WP Engine with "disruptive measures" if it failed to comply with the requirements, including paying a percentage of gross revenue. In response, Automattic also sent a cease and desist letter to WP Engine, accusing the company of infringing on the WordPress and WooCommerce trademarks.
Separately, the WordPress Foundation told TechCrunch that WP Engine violated the Foundation's trademark policy. "No one has the right to use WordPress trademarks as part of a product, project, service, domain name, or company name. WP Engine has repeatedly violated this policy, and Automattic's letter provides examples of such violations", the foundation said in a statement.
Shortly after the blocking of WP Engine on WordPress.org, Mullenweg wrote in his blog that the main controversial issue is trademarks. He noted that Automattic has been trying to enter into a licensing agreement with WP Engine for a long time, offering either the payment of a license fee or a contribution to the development of an open source project. However, what exactly is meant by the contribution, Mullenweg did not specify.
Source
The scandal around WordPress.org escalated - the management of the resource blocked the hosting provider WP Engine from accessing its resources. This decision is due to disagreements between WordPress co-founder and Automattic CEO Matt Mullenweg and WP Engine.
Mullenweg stated that WP Engine will not have access to the platform's resources, including themes and plugins, until legal issues are resolved. He noted that WP Engine aims to take control of the WordPress user experience by managing authorization systems, server updates, and directories of plugins, themes, blocks, and other resources.
Mullenweg emphasized that WP Engine can offer its customers its redesigned version of the WordPress code under the GPL license and provide its services. But WP Engine servers will no longer be able to connect to WordPress resources for free. As a result of the ban, WP Engine users are deprived of the ability to install plugins and update themes through WordPress.org.
Many WordPress developers and supporters have expressed concerns that such a restriction could prevent WP Engine users from receiving security updates, potentially leaving sites vulnerable. In turn, WP Engine acknowledged the problem and announced that it was working on a solution, noting that the ban does not affect the performance, reliability or security of sites, as well as the ability to make changes to code or content.
It's important to understand that WordPress powers nearly 40% of the websites on the internet through various hosting providers, including Automattic and WP Engine. Users can also take an open-source project and launch websites on their own, but many prefer to use plug-and-play solutions.
The standoff between WP Engine and Automattic began last week when Mullenweg publicly accused WP Engine of profiteering and called the company a "WordPress cancer". According to Mullenweg, the company doesn't contribute enough to the WordPress community, even though both it and Automattic make about half a billion dollars annually.
Amid the allegations, WP Engine sent a letter to Mullenweg and Automattic demanding that they stop spreading such claims. The letter alleges that Automattic threatened WP Engine with "disruptive measures" if it failed to comply with the requirements, including paying a percentage of gross revenue. In response, Automattic also sent a cease and desist letter to WP Engine, accusing the company of infringing on the WordPress and WooCommerce trademarks.
Separately, the WordPress Foundation told TechCrunch that WP Engine violated the Foundation's trademark policy. "No one has the right to use WordPress trademarks as part of a product, project, service, domain name, or company name. WP Engine has repeatedly violated this policy, and Automattic's letter provides examples of such violations", the foundation said in a statement.
Shortly after the blocking of WP Engine on WordPress.org, Mullenweg wrote in his blog that the main controversial issue is trademarks. He noted that Automattic has been trying to enter into a licensing agreement with WP Engine for a long time, offering either the payment of a license fee or a contribution to the development of an open source project. However, what exactly is meant by the contribution, Mullenweg did not specify.
Source
