Automattic Receives Backlash for Cloning Premium Plugin  🔗 **Source:** [Automattic Receives Backlash for Cloning Premium Plugin](https://www.searchenginejournal.com/automattic-receives-backlash-for-cloning-premium-plugin/533589/) > [!note]+ Document Notes > tags: [#wordpress, #plugin_conflict, #automattic, #acffork, #opensource, #ethicaldebate] > - #wordpress > - #plugin_conflict > - #automattic > - #opensource > - #ethicaldebate > Author: [Roger Montti] > Source: [Search Engine Journal](https://www.searchenginejournal.com/automattic-receives-backlash-for-cloning-premium-plugin/533589/?__readwiseLocation=) > Reference: [Full Article Link](https://www.searchenginejournal.com/automattic-receives-backlash-for-cloning-premium-plugin/533589/?__readwiseLocation=) > date created: 2024-11-26 > > # Title: Automattic Receives Backlash for Forking Premium Plugin ACF > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) 3. [📖 References](#-references) 4. [🗣️ Paraphrase](#-paraphrase) 5. [📰 Newsletter](#-newsletter) 6. [✅ Action Items](#-action-items) 7. [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) 8. [❓ Questions](#-questions) 9. [🔮 Future Research](#-future-research) 10. [💡 Implications](#-implications) 11. [🧠 Learning Styles Assessment](#-learning-styles-assessment) 12. [📊 Accessibility Assessment](#-accessibility-assessment) 13. [🌍 DEIB Assessment](#-deib-assessment) 14. [✅ Logical Validity](#-logical-validity) 15. [🔍 DARVO Analysis](#-darvo-analysis) 16. [🔍 SEO Evaluation](#-seo-evaluation) 17. [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: The article examines Automattic’s decision to fork the Advanced Custom Fields (ACF) plugin, originally a premium offering by WP Engine. The move has drawn widespread criticism for ethical implications, perceived software piracy, and disruption to the WordPress ecosystem. The backlash highlights concerns over the legality, morality, and long-term effects of redistributing a premium product for free under the guise of open-source practices. --- ## 📖 Main Content: ### 🗒️ Notes #### **1. Automattic’s Forking Actions** - **Timeline of Events** - October 3, 2024: WP Engine implemented independent update capabilities for ACF to bypass WordPress.org restrictions. - October 12, 2024: Automattic forked ACF, renaming it Secure Custom Forms (SCF) and published it on WordPress.org. - WP Engine alleged that Automattic removed copyright notices and license checks, sparking debate over legality. - **Key Allegations Against Automattic** - Redistributing a premium product for free undermines the established freemium business model. - Removal of copyright details potentially violates software licensing norms. --- #### **2. Community Reaction** - **Developer Backlash** - Developers argue Automattic’s actions harm competitors like Meta Box by offering similar premium features for free. - Meta Box users expressed frustration, fearing financial losses due to market disruption. - **Social Media Criticism** - Reddit and Facebook groups saw unanimous disapproval, with claims Automattic’s actions resemble piracy. - Criticisms included accusations of hypocrisy, noting Automattic’s past actions against pirated plugins. - **Concerns for WordPress Ecosystem** - Many fear the move sets a precedent that could destabilize plugin monetization strategies. - Trust in WordPress.org governance is questioned due to perceived favoritism and double standards. --- #### **3. Open-Source Ethics Debate** - **Legalities of Forking** - Forking is a valid practice under open-source licenses, but ethics are debated when it impacts commercial viability. - Critics argue Automattic’s fork is “legal theft” due to the removal of license enforcement. - **Impact on Freemium Business Models** - Freemium developers rely on goodwill from free offerings to convert users to paid versions. - Automattic’s actions threaten this balance, deterring future innovation. --- ## 🔍 DARVO Analysis ### **Deny** - **Example:** - Automattic justified forking by citing a security vulnerability in ACF, downplaying WP Engine’s version updates as inadequate. - **Impact:** - This reframing shifts focus from Automattic’s controversial redistribution to WP Engine’s alleged failings. --- ### **Attack** - **Example:** - Automattic claimed WP Engine’s lawsuit drove the need for action, positioning the company as the aggressor. - **Impact:** - Frames WP Engine as litigious and uncooperative, shifting blame for the controversy. --- ### **Reverse Victim and Offender** - **Example:** - Automattic cast themselves as stewards of WordPress security, positioning the fork as a protective measure rather than an opportunistic move. - **Impact:** - Attempts to portray Automattic as a victim of WP Engine’s alleged neglect, reversing public sympathy. --- ### Emotional and Logical Cues - **Tone:** Defensive and assertive, aimed at justifying actions while deflecting criticism. - **Logical Fallacies:** Potential strawman in framing WP Engine as negligent without substantiating claims. --- ## 📖 References: - Montti, R. (2024). [Automattic Receives Backlash for Cloning Premium Plugin](https://www.searchenginejournal.com/automattic-receives-backlash-for-cloning-premium-plugin/533589/?__readwiseLocation=). --- ## 🗣️ Paraphrase: 1. **Original:** "Automattic cloned the premium ACF plugin and is distributing it for free; the WordPress community responds with unanimous disapproval." **Paraphrase:** "By forking the ACF plugin and making it freely available, Automattic has faced widespread criticism from the WordPress community." 2. **Original:** "Many fear the move could destabilize the plugin ecosystem and undermine developers’ ability to monetize their work." **Paraphrase:** "The decision raises concerns about its potential to disrupt plugin developers’ revenue models and destabilize the broader ecosystem." --- ## 📰 Newsletter: **Headline:** Controversy Hits WordPress as Automattic Forks Premium Plugin **Blurb:** Automattic’s decision to fork WP Engine’s ACF plugin has sparked debate across the WordPress ecosystem. Critics accuse Automattic of undermining ethical plugin practices and jeopardizing the freemium model that sustains open-source innovation. Discover the key arguments, legal implications, and community response in our latest issue. [Read more](https://www.searchenginejournal.com/automattic-receives-backlash-for-cloning-premium-plugin/533589/?__readwiseLocation=). --- ## ✅ Action Items: 1. **Professional Engagement:** - Host discussions on open-source ethics and monetization at WordPress meetups. - Develop case studies analyzing plugin disputes for WordPress contributors. 2. **DEIB Advocacy:** - Ensure equitable treatment in plugin repositories to maintain trust across diverse developers. 3. **Educational Outreach:** - Include licensing best practices in WordPress training materials. --- ## 🎯 Conclusion: Automattic’s controversial decision to fork ACF challenges the balance between open-source freedoms and ethical business practices. The case highlights a critical need for clearer governance and consistent ethical standards in the WordPress ecosystem. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Automattic Receives Backlash for Cloning Premium Plugin|Automattic Receives Backlash for Cloning Premium Plugin, Roger Montti]] ## Highlights - One of the Facebook group members remarked that no, they didn’t make a bad decision by purchasing a license for Meta Box, saying that Matt Mullenweg was the one that made the poor decision. Another group member expressed that he regarded Mullenweg as an unreliable steward of the ACF fork and wouldn’t trust his fork, ACF, on any of the websites he develops. ([View Highlight](https://read.readwise.io/read/01jdmrbt0zmj7wt03nn75j872x))