The ACF>SCF ‘Fork’ and Legal Risk  🔗 **Source:** [The ACF>SCF ‘Fork’ and Legal Risk](https://wpandlegalstuff.com/the-acfscf-fork-and-legal-risk/) > [!note]+ Document Notes > tags: [#wordpress, #plugin, #legalrisk, #wpeengine, #opensource] > Author: Richard Best > Source: WP and Legal Stuff > Reference: [The ACF>SCF ‘fork’ and legal risk](https://wpandlegalstuff.com/the-acfscf-fork-and-legal-risk/) > date created: 2024-10-14 11:05 > > # Title: The ACF>SCF ‘fork’ and legal risk > <!-- deep-read:sections start --> ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: This article discusses the legal and ethical implications of WordPress forking the ACF plugin into "Secure Custom Fields" following disputes with WP Engine. It questions whether the fork truly follows GPL guidelines, explores potential trademark infringement, and highlights the tension between WordPress governance and commercial interests. ## 📖 Main Content: The move by WordPress to replace ACF with Secure Custom Fields has sparked debates about legality and ethics. The article scrutinizes how trademarks and copyrights could apply to plugin repositories and the limits of GPL permissions. It further reflects on the implications for WordPress governance and trust in the community. ### 🗒️ Notes: - **Legal Concerns**: Issues raised include GPL compliance, copyright usage, and trademark risks. - **Ethics**: Concerns that the fork sets a troubling precedent within the WordPress ecosystem. - **Plugin Governance**: Calls attention to tensions between governance and commercial interests in open-source communities. ## 📖 References: - [The ACF>SCF ‘fork’ and legal risk](https://wpandlegalstuff.com/the-acfscf-fork-and-legal-risk/) ## 🗣️ Paraphrase: 1. The article suggests that the GPL might not fully permit WordPress’s actions, raising concerns over copyright and trademark implications. 2. It argues that replacing ACF with SCF appears to be driven more by legal disputes than genuine security needs. ## 📰 Newsletter: This week’s issue covers the controversial ACF-to-SCF fork by WordPress. We explore what this means for plugin governance, legal risks involved, and how developers are responding. Stay informed on plugin changes and tips to safeguard your projects from governance issues in open-source communities! ## ✅ Action Items: - **Governance Learning**: Apply lessons from this incident to refine governance practices. - **OSPO Relevance**: Understanding these challenges helps you align strategies for future OSPO leadership. ## 🧪 Hypotheses: - Future plugins may move to decentralized platforms to avoid governance disputes. - Plugin takeovers could deter developers from contributing to WordPress. ### 📊 Methodology: - **Survey**: Gauge community sentiment on plugin governance. - **Case Study**: Compare governance models in other open-source ecosystems. ### ❓ Questions: - How can plugin developers protect their work from involuntary forks? - What governance models would foster transparency in plugin ecosystems? ### 🔮 Future Research: - Investigate alternative governance frameworks for plugins. - Assess the impact of plugin forks on user trust and community participation. ### 💡 Implications: A shift towards better governance models could strengthen trust and engagement in the WordPress ecosystem. ### 🧠 Learning Styles Assessment: - **Visual Learners**: Add diagrams to explain legal processes. - **Logical Learners**: Provide legal precedent examples. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure legal documentation is accessible. - **Keyboard Navigation**: Improve accessibility for governance discussion platforms. ### 🌍 DEIB Assessment: - **Inclusiveness**: Foster open discussions on governance. - **Psychological Safety**: Encourage constructive feedback from contributors. ### ✅ Logical Validity: - **Strengths**: Well-reasoned analysis on legal and governance issues. - **Fallacies**: Some reliance on slippery slope arguments regarding governance risks. ### 🔍 SEO Evaluation: - **Keywords**: ACF fork, SCF plugin, WordPress governance. - **Optimization**: Link to legal documentation to enhance engagement. ## 🎯 Conclusion: The ACF-to-SCF fork raises important questions about governance and legality within the WordPress ecosystem. As this case unfolds, it highlights the need for clear guidelines and transparent governance models to maintain community trust. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/The ACFSCF ‘Fork’ and Legal Risk|The ACF>SCF ‘Fork’ and Legal Risk, Richard Best]] ## Highlights - Ethics Regardless of what the GPL may allow (more on that below), people are and will be questioning the ethics of this so-called fork, despite what they may feel about WP Engine’s level of contribution to the community. We’re not talking here about a small plugin that was in dire need of updates. We’re talking about one of the most popular plugins in the ecosystem with 2 million+ users, a long and trusted development history behind it, and trusted developers maintaining it. ([View Highlight](https://read.readwise.io/read/01ja5nwqa8cvaqpnz8j3cmf8pn)) - If a repository operator takes a third party’s existing codebase which that third party put in the repository and is actively maintaining and developing, and takes control of and changes that actual codebase rather than duplicating it in a separate repository (or sub-repository) and *then* modifying it, is that a true fork and, if not, is it permitted by the GPL? ([View Highlight](https://read.readwise.io/read/01ja5nxr3a24c8c8czdrq1brmg)) - Any argument that this has nothing to do with commerce would probably be weak, because the announcement post on WordPress.org states: “Similar situations have happened before, but not at this scale. This is a rare and unusual situation brought on by WP Engine’s legal attacks, we do not anticipate this happening for other plugins.” ([View Highlight](https://read.readwise.io/read/01ja5nzhsdxfxtmkmxxprxk2z7))