Kevin Brkal的动态

The WordPress community is in disarray thanks to two billion-dollar companies (WP Engine and Automattic) taking their corproate conflict to the public, and forcefully making WordPress contributors part of it. Here is my summary any analysis of the situation. I see this conflict fitting into a trend of billion-dollar companies built on open source increasingly struggling to monetize/generate profits, and live up to their high 2021 valuations. They need to find a way to grow: and several are forced to turn to things like changing the license for their product to no longer be open source. Automattic is attempting to use a trademark to get what they want: market share from WP Engine, or to force a sale of the company that Automattic was previously an investor in. Read the longer analysis, with the timeline: https://lnkd.in/ejzmH_uY

WordPress has banned WP Engine from accessing its free resources, impacting thousands of websites. But why? Here’s a breakdown of what led to this: 1?? Matt Mullenweg, co-creator of WordPress, accused WP Engine of trademark infringement, asking for millions in compensation. 2?? WP Engine failed demands and WordPress openly criticized their limited contributions to the community. 3?? A legal standoff began with cease-and-desist letters from both sides, leading to a ban that affects WP Engine users' ability to install or update plugins via wp-admin. While WP Engine is working on a fix, customers are left in a difficult situation. Is your site affected? We can help! At Inventiff. ／Creative digital solutions. we have a dedicated team of WordPress development experts who can help you navigate these changes.

WordPress has banned WP Engine from accessing its free resources, impacting thousands of websites. But why? Here’s a breakdown of what led to this: 1?? Matt Mullenweg, co-creator of WordPress, accused WP Engine of trademark infringement, asking for millions in compensation. 2?? WP Engine failed demands and WordPress openly criticized their limited contributions to the community. 3?? A legal standoff began with cease-and-desist letters from both sides, leading to a ban that affects WP Engine users' ability to install or update plugins via wp-admin. While WP Engine is working on a fix, customers are left in a difficult situation. Is your site affected? We can help! We have a dedicated team of WordPress development experts who can help you navigate these changes.

Matt Mullenweg and WP Engine are currently at odds over the direction of WordPress. At the 2024 WordCamp US conference, Matt Mullenweg, CEO of Automattic, made a bold statement, calling WP Engine a "cancer to WordPress." He criticized the hosting company's business practices, suggesting that they profited off the WordPress ecosystem without giving back to its development. This sentiment sparked significant debate within the community, as Mullenweg emphasized the disparity between what Automattic and other companies invest in WordPress. But it didn’t end there. WP Engine, a leading WordPress hosting platform, responded swiftly. They filed legal action against Automattic, accusing Mullenweg of defamation and making false claims. According to WP Engine, the issue wasn’t just about the comments at WordCamp; they also alleged that Mullenweg had demanded a substantial payment from WP Engine before the event, which they refused. This legal battle has caused ripples in the WordPress community, raising questions about how companies should contribute to open-source projects and what role commercial entities play in the broader ecosystem. It’s a tense situation, with two major players locked in a dispute, and the future impact on WordPress is yet to unfold. Follow Rilwanu Isyaku to stay in the loop. #matt #wordpress #wpengine #automattic #trends

The WordPress vs WP Engine Drama Explained in Plain Words! The recent tension between WordPress and WP Engine revolves around their differing approaches to open-source values and business practices. Here’s a quick breakdown: 1. WordPress’ Concerns: WordPress accuses WP Engine of prioritizing profit over the open-source community by restricting certain features to premium users. 2. WP Engine’s Defense: WP Engine claims these premium services ensure better performance and security, adding value to their customers. 3. Community Reaction: The debate has sparked discussions about how companies can balance open-source ideals with commercialization while still delivering value. Right now, the WordPress vs. WP Engine conflict is causing a lot of buzz in the tech community. It stems from disagreements over open-source licensing, with WordPress criticizing WP Engine for using its platform in ways that allegedly break GPL (General Public License) rules. This debate has led to a wider discussion about the balance between open-source freedom and commercial tools within the WordPress ecosystem. The conversation is ongoing, with both sides presenting valid perspectives. #WordPressDrama #WPEngineDebate #OpenSourceConflict #TechDisputes #GPLIssues #WebDevelopmentTalks #OpenSourceVsProprietary #TechCommunityBuzz

"Levelling up our online presence with a sleek new Techy Geeks webpage model crafted on WordPress! ?? Dive into a world of tech innovation and insights. Explore now: [ https://lnkd.in/gfXX9rEB ] #WordPressWonder #TechJourney"

?? Breaking: Tensions Escalate Between Automattic and WP Engine Over WordPress Usage ?? In a heated dispute that has rocked the WordPress community, Automattic CEO and WordPress co-founder Matt Mullenweg has publicly criticized WP Engine, calling them a "cancer to WordPress" during WordCamp US 2024. The conflict stems from WP Engine disabling the revision history feature and accusations of not contributing enough to the open-source project. ?? Automattic demands that WP Engine either contribute 8% of its revenue to WordPress development or face trademark license fees. WP Engine has hit back with cease-and-desist letters and renamed its plans to avoid WordPress references. ?? The WordPress Foundation has also updated its Trademark Policy, signaling further developments in this high-stakes battle. ??? Stay tuned as this dispute unfolds, and the WordPress community watches closely for the next move. ?? #WordPress #Automattic #WPEngine #TechNews #DigitalMarketing #WebDevelopment #OpenSource #WPCommunity

BREAKING: The trademark dispute between WordPress/Automattic and WP Engine has escalated. Here's what you need to know: Legal Moves: Following a cease-and-desist from WP Engine, Automattic has now issued their own, citing unauthorized use of WordPress and WooCommerce trademarks. Service Impact: WordPress.org blocks WP Engine from plugin updates, potentially affecting security & functionality for WP Engine users. Community Buzz: The tech community on platforms like X is buzzing with debate. Opinions split on whether this is about trademark protection or competition stifling. We are following this case closely for our clients to minimise any potential impact. Stay tuned as this story develops. It's more than a legal battle; it's shaping the future of open-source software use in business.

Matt Mullenweg,?CEO of Automattic, has misused his control of WordPress to interfere with?WP Engine customers’ access to?https://WordPress.org,?asserting that he did so because WP Engine filed litigation against https://Wordpress.org. This simply is not true. Our Cease & Desist letter was a letter – not a lawsuit – and was directed at Automattic for Matt’s pattern of serious and repeated misconduct – behavior that must stop for the health and stability of the entire community. Matt Mullenweg’s?unprecedented?and unwarranted?action interferes with the normal operation of the entire WordPress ecosystem, impacting not just WP Engine and our customers, but all WordPress plugin developers and open-source users who depend on WP Engine tools like ACF.?We are taking immediate steps to remediate the impact of this action. We remain steadfastly committed to supporting WP Engine customers, users, and the entire WordPress community.

I'm a WP Engine user - honestly didn't even know about auto-updates being removed. That's a massive issue. The bigger problem here though is just how massively childish this whole thing is. Does it sound like WP Engine, now a VC-run profit-driven conglomerate, is being selfish and taking considerably more than they're bringing back to the WP ecosystem? Yes. Did the WordPress legal language allow for that type of usage? Also yes. We use WordPress because - for the most part - we don't have to worry about boneheaded decisions by upper management that affect our daily lives. It's open-source, so I don't need to be concerned about them jacking up prices without alternatives or any handful of other things that we've come across without proprietary service providers. Except, now apparently that's not the case. Automatic has now shown that they're willing to completely screw over a huge swath of users - opening sites up to tremendous risk - because their founder is apparently a child that's angry that somebody took advantage of their license. Not an indicator I look for when we're looking for service providers for our clients - it definitely makes me rethink our software offerings. #copied