WordPress: The Drama Continues  🔗 **Source:** [WordPress: The Drama Continues](https://eric.mann.blog/wordpress-the-drama-continues/) > [!note]+ Document Notes > tags: [#WordPress, #ACF, #open-source, #plugins, #drama] > Author: Eric Mann > Source: Eric Mann’s Blog > Reference: [WordPress: The Drama Continues](https://eric.mann.blog/wordpress-the-drama-continues/) > date created: 2024-10-15 21:45 > > # Title: WordPress: The Drama Continues > <!-- 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-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ## 📝 Summary: This article addresses the controversy around the WordPress.org team forking the Advanced Custom Fields (ACF) plugin, following a legal dispute with WP Engine. It explores both perspectives—WP Engine's claim of unfair treatment and the WordPress.org team's justification for prioritizing user security. ## 📖 Main Content: The dispute began as WP Engine sued WordPress co-founder Matt Mullenweg over trademarks. WP Engine's ban from WordPress.org repositories led to forking ACF into a new "Secure Custom Fields" plugin. The article highlights challenges with user communication and the legal complexities surrounding trademarks. While acknowledging the controversy, Eric Mann ultimately supports the WordPress.org team’s decision, emphasizing the importance of end-user security. ### 🗒️ Notes: - **Context:** ACF was forked into "Secure Custom Fields" due to WP Engine's ban from WordPress.org. - **Fork Justification:** Ensures continuous security updates for users. - **Challenges:** Legal disputes over trademark usage complicate the situation. - **Personal Insight:** Mann, despite disagreements with Mullenweg, supports the decision from a security standpoint. ## 📖 References: - [Eric Mann Blog](https://eric.mann.blog/wordpress-the-drama-continues/) ## 🗣️ Paraphrase: 1. Mann acknowledges that while forking is controversial, user security outweighs the politics. He notes that informing users about the fork is a challenge, especially given the non-technical nature of many WordPress users. 2. Despite legal tensions, Mann suggests that the WordPress team’s move to fork ACF was necessary to prevent potential vulnerabilities due to WP Engine's restricted ability to push updates. ## 📰 Newsletter: 🚀 **WordPress Plugin Drama – ACF Forked** Big news from the WordPress world! WordPress.org has officially forked the popular ACF plugin into "Secure Custom Fields" amid a legal dispute with WP Engine. While some see the move as heavy-handed, it ensures critical security updates for users. WP Engine’s legal battle complicates things, but the fork ensures continuity. Dive deeper into the story and how it impacts WordPress developers [here](https://eric.mann.blog/wordpress-the-drama-continues/). ## ✅ Action Items: - Assess how the fork impacts plugin support workflows at GoDaddy. - Explore opportunities for fostering community transparency through newsletters or forums. - Monitor the security response from the new plugin team to ensure alignment with GoDaddy’s open-source practices. ## 🧪 Hypotheses: 1. Forking a popular plugin improves user security but might reduce community trust. 2. Legal disputes in open-source ecosystems discourage collaboration and innovation. ### 📊 Methodology: - **Data Sources:** Track updates and user feedback across social media and forums. - **Research Design:** Analyze plugin adoption metrics before and after the fork. - **Analysis:** Use sentiment analysis on relevant discussions to gauge community reactions. ### ❓ Questions: - How can WordPress balance community transparency with security concerns? - Will the forked plugin retain the same level of community support? ### 🔮 Future Research: - Investigate how forks impact user trust and plugin adoption. - Explore strategies for mitigating legal conflicts in open-source communities. ### 💡 Implications: Research into forking dynamics could inform policies on open-source project management and user security protocols. ### 🧠 Learning Styles Assessment: - **Visual Learners:** Lacks diagrams; recommend adding infographics on the legal context. - **Aural Learners:** Provide audio summaries for non-developers. - **Verbal Learners:** Strong narrative format with anecdotal insights. - **Physical Learners:** Suggest real-world exercises on forking and plugin management. - **Logical Learners:** Well-structured argumentation on balancing security and legality. - **Social Learners:** Encourage community discussions on similar issues. - **Solitary Learners:** Offers reflections for independent learning. - **Naturalistic Learners:** No environmental or sustainability elements to enhance. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility:** Ensure alt-text for plugin-related visuals. - **Keyboard Navigation:** Optimize any interactive elements for accessibility. - **Contrast and Readability:** Use high-contrast themes for articles. - **Text Resizing:** Ensure responsive design. ### 🌍 DEIB Assessment: - **Cultural Relevance:** Limited diversity—introduce more community voices. - **Inclusive Language:** Use simplified terms for non-technical readers. - **Neurodiversity Support:** Break text into more digestible sections. - **Representation:** Add examples from diverse backgrounds. - **Psychological Safety:** Include a disclaimer acknowledging varied viewpoints. ### ✅ Logical Validity: - **Strengths:** Clear causal reasoning linking forking to security concerns. - **Weaknesses:** Lacks detailed legal evidence for claims. - **Suggestions:** Provide case studies on successful plugin forks to support arguments. ### 🔍 SEO Evaluation: - **Keywords:** Use more specific long-tail keywords like "WordPress plugin fork." - **Meta Description:** Add a concise summary with relevant keywords. - **Headers:** Utilize H2s to improve readability. - **Internal Links:** Link to related WordPress community resources. - **Social Sharing:** Optimize Open Graph tags for social media visibility. ## 🎯 Conclusion: Eric Mann’s article sheds light on the nuanced dynamics of forking within WordPress, balancing legal disputes and security priorities. Despite differing opinions, the WordPress team’s decision to fork ACF highlights the importance of prioritizing user safety. --- <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WordPress The Drama Continues|WordPress: The Drama Continues, Eric Mann]] ## Highlights - Creating and maintaining a fork raises several tricky issues: • How will the team inform and educate end users about the fork? Remember, most *users* of WordPress aren’t developers in the first place. Just explaining a fork is tricky – also explaining the politics behind why the fork exists is harder still. • Given the active legal dispute began over trademark misuse, how can Matt and his team continue to provide updates (even if just for security) to ACF users without risking a further legal battle over potential misuse of ACF’s trademarks? ([View Highlight](https://read.readwise.io/read/01ja9ejmrtz8w9nx5794szxb0b))