I Tried to Explain the Whole Wordpress Drama  🔗 **Source:** [I Tried to Explain the Whole Wordpress Drama](https://youtube.com/watch?v=XSb4Lul0qlc&si=LVif6Nz7B5F9hUEf) > [!note]+ Document Notes > tags: [#WordPress, #opensource, #businessdrama] > - #MattMullenweg > - #WPCommunity > - #Automattic > > Author: Theo > Source: [I tried to explain the whole WordPress drama](https://www.youtube.com/watch?v=XSb4Lul0qlc) > Reference: Transcript of video provided > date created: 2024-10-15 10:00 > > # Title: WordPress Drama and the Conflicts within Its Ecosystem > <!-- deep-read:sections start --> ## Table of Contents: 1. [📝 Summary](#-summary) 2. [📖 Main Content](#-main-content) 3. [🗒️ Notes](#️-notes) 4. [🗣️ Paraphrase](#-paraphrase) 5. [📰 Newsletter](#-newsletter) 6. [✅ Action Items](#-action-items) 7. [🧪 Hypotheses](#-hypotheses) 8. [📊 Methodology](#-methodology) 9. [❓ Questions](#-questions) 10. [🔮 Future Research](#-future-research) 11. [💡 Implications](#-implications) 12. [🧠 Learning Styles Assessment](#-learning-styles-assessment) 13. [📊 Accessibility Assessment](#-accessibility-assessment) 14. [🌍 DEIB Assessment](#-deib-assessment) 15. [✅ Logical validity](#-logical-validity) 16. [🔍 SEO Evaluation](#-seo-evaluation) 17. [🎯 Conclusion](#-conclusion) ## 📝 Summary: This transcript covers the intricate conflicts in the WordPress community, especially focusing on tension between Matt Mullenweg (CEO of Automattic) and WP Engine. The transcript explains the separation between WordPress.org, Automattic, and the WordPress Foundation, and delves into how financial interests, licensing rights, and personal grudges influence these dynamics. ## 📖 Main Content: - **Ownership Structure**: - WordPress.com is run by Automattic for hosting and services. - WordPress.org provides plugin registries but is controlled operationally by Automattic. - The WordPress Foundation holds the trademark but gave Automattic exclusive commercial licensing. - **Matt’s Grudges**: - Conflicts often stem from Matt feeling that companies like WP Engine benefit from WordPress without contributing enough ("Five for the Future"). - He has also been protective about GPL licensing, causing conflicts with developers of premium themes (e.g., the Thesis theme). - **Commercial Tensions**: - Companies like WP Engine are preferred hosts but have strained relationships with Automattic. - Matt's complaint centers on these companies profiting from WordPress without matching Automattic's contributions. - **The Five for the Future Initiative**: - Automattic expects companies profiting from WordPress to contribute 5% of their time/resources to WordPress development. ## 🗒️ Notes: - **Structure and Conflicts**: - **WordPress.com** focuses on hosting. - **WordPress.org** handles code and plugins. - **Automattic** wields operational control despite separation. - **Key Tensions**: - **Trademark Licensing**: Controlled by Automattic despite the Foundation's ownership. - **Grudge Against WP Engine**: Matt feels WP Engine profits disproportionately. - **GPL Issues**: Conflict with developers who tried to gatekeep premium themes under proprietary licenses. - **Key Observations**: - High code turnover within WordPress: ~80% churn annually. - Automattic seeks compliance with its 5% contribution rule. ### 1. **Introduction and Context** - **[0:00 - 0:15]**: Merlin greets the audience and introduces the focus of the discussion: the ongoing drama in the WordPress community. - **[1:00 - 3:30]**: Guest Dan introduces himself, providing background on his work with TinyChat, startups, and the current topic. - **Key Insight**: Merlin hints that both sides in the WordPress conflict have valid yet opposing perspectives. --- ### 2. **WordPress Structure and Separation** - **[17:00 - 28:00]**: - Overview of the blurred lines between: - **WordPress.com**: Hosting and commercial services by Automattic. - **WordPress.org**: The open-source code repository. - **WordPress Foundation**: Nonprofit holding the WordPress trademark. - **[21:00]**: Discussion of the split in control: - Automattic has operational authority over WordPress.org despite the official separation. - The WordPress Foundation owns the trademark but licensed it commercially to Automattic, leading to complaints of control issues. - **Important Note**: Automattic’s exclusive licensing of the trademark is perceived as both strategic and problematic. --- ### 3. **Matt Mullenweg’s Grudges and Personal Conflicts** - **[30:00 - 48:00]**: - **Thesis Theme Conflict**: Matt opposed premium themes, like **Thesis**, for violating the GPL (General Public License). - Developers wanted to gate premium features behind paywalls, which Matt saw as contradictory to open-source principles. - **[35:00]**: Matt’s "nuclear" response included spending **$100k to acquire thesis.com** just to block the theme creator from using it. - **Key Takeaway**: Matt’s personal actions highlight how the lines between personal and professional conflicts can blur within open-source governance. --- ### 4. **Automattic’s Control and the 'Five for the Future' Initiative** - **[54:00 - 75:00]**: - Matt’s initiative encourages companies benefiting from WordPress to contribute **5% of resources** to the project. - **Issue Raised**: Many hosting providers, especially **WP Engine**, fall short of this contribution, causing friction. - **[65:00]**: Matt compares Automattic’s 3,000 engineering hours against WP Engine’s 40 hours per week, framing this as unfair. - **Guest's Critique**: The analogy of running a marathon – “Just because you run 40 miles doesn’t mean everyone else must.” - **Tension Point**: Matt uses this initiative as a benchmark to criticize hosting companies, adding to his list of grudges. --- ### 5. **WP Engine and Market Dynamics** - **[80:00 - 98:00]**: - **WP Engine**: Grows rapidly, becoming the most reliable WordPress host, surpassing WordPress.com. - They acquire key plugins, such as **Advanced Custom Fields (ACF)** and **WP GraphQL**. - **[84:00]**: ACF becomes essential to users for building structured content, even though it is technically an external plugin. - **Key Friction**: WP Engine’s success and plugin ownership provoke Matt, who sees them as benefiting without adequate contributions. --- ### 6. **Licensing Conflicts: WordPress Trademark Control** - **[100:00 - 120:00]**: - The WordPress Foundation holds the trademark but licenses it exclusively to Automattic. - **[110:00]**: This leads to tension with hosting providers needing to pay Automattic for the right to use the WordPress name commercially. - **Matt’s Complaint**: Even **his mother mistook WP Engine for an official WordPress project** because of its name. --- ### 7. **Open Source and Governance Issues** - **[130:00 - 150:00]**: - Discussion on Matt’s strict GPL enforcement, his distrust of companies like **Silver Lake**, and the challenges of running an open-source project with **80% code churn annually**. - **[138:00]**: Matt’s frustration grows as WP Engine and other hosts benefit without needing to contribute to WordPress at his desired level. - **Conflict Point**: Matt perceives these companies as taking advantage of the open-source ecosystem without giving back sufficiently. --- ### 8. **Community and Hosting Market Overview** - **[155:00 - 175:00]**: - Breakdown of key WordPress hosts: WP Engine, WordPress.com, and **Bluehost**. - **WP Engine**: The most preferred host among professionals. - **Bluehost**: Another major player, though with a smaller market share. - **[160:00]**: Revenue Analysis: - WP Engine earns **$400 million annually**, surpassing WordPress.com in profitability. - **Observation**: While smaller hosting providers exist, WP Engine and Automattic control the bulk of the WordPress hosting market. --- ### 9. **Future Directions and Conflict Predictions** - **[180:00 - 200:00]**: - **Merlin’s Recommendation**: Fork the plugin system and create a truly open ecosystem to reduce Automattic’s influence. - **Predicted Outcome**: WP Engine might support such a fork, given their growing dissatisfaction with Automattic’s demands. - **Insight**: If the community fragments, Automattic’s control over WordPress.org may weaken. --- ### 10. **Philosophical and Governance Challenges in Open Source** - **[205:00 - 220:00]**: - Discussion on the paradox of open-source projects: Contributors provide value, yet companies benefit without necessarily giving back. - **Analogy with ElasticSearch**: - Open-source projects are often exploited by large corporations, such as Amazon with **ElasticSearch**. - **[210:00]**: The ElasticSearch licensing conflict parallels the WordPress drama, as WP Engine benefits without substantial contributions. --- ### 11. **Conclusion: Open Source Governance is Messy** - **[230:00 - 250:00]**: - **Summary of the Drama**: - Matt’s personal investment in WordPress fuels his grudges, creating friction with other companies. - Despite WordPress being open-source, Automattic wields significant control over its ecosystem. - **Key Insight**: The open-source community struggles with balancing control, contributions, and commercial interests, leading to inevitable conflicts. - **[240:00]**: Merlin concludes that **open-source governance** is inherently difficult, and personal conflicts often escalate into broader issues within the community. ### 1. **Introduction of GoDaddy in the Context of Conflicts** - **[838:56 - 845:24]** - **Brief Mention**: - Merlin touches upon a conflict between **Matt Mullenweg** and GoDaddy. - **Details remain vague**, with Merlin stating that he doesn't know the specifics but confirms that the conflict occurred due to GoDaddy's involvement in WordPress hosting. --- ### 2. **Matt’s Disputes with Hosting Providers** - **[840:12 - 857:75]** - **Conflict Context**: - Matt had **similar spats** with other major hosting companies like **Bluehost**, which stemmed from their role in the **WordPress hosting ecosystem**. - Merlin emphasizes that both disputes—GoDaddy and Bluehost—centered around **Matt’s grievances with companies profiting from WordPress** but not contributing enough engineering hours or financial resources back into the project. --- ### 3. **Resolution with GoDaddy and Other Hosts** - **[854:16 - 860:12]** - **Outcome**: - While Merlin doesn’t elaborate on the details of the resolution, he suggests that **GoDaddy, Bluehost, and other hosts** seem to have **come to an agreement** with Automattic. - Merlin implies that these companies might have started **paying some form of fee** to Automattic to **use the WordPress brand** in their marketing and hosting services. --- ### 4. **GoDaddy's Hosting Role in the WordPress Ecosystem** - **[1263:32 - 1270:28]** - **Market Overview**: - **GoDaddy** is mentioned as one of the platforms hosting **“crappy” WordPress sites for free**, illustrating that many low-tier WordPress sites are **hosted on cheaper or promotional services**. - This points to GoDaddy’s **role in the hosting ecosystem** as a more accessible, budget-friendly option compared to **premium hosts like WP Engine**. --- ### 5. **Revenue and Market Dynamics** - **[1268:60 - 1281:88]** - **GoDaddy’s Position in the Market**: - Although **GoDaddy hosts many WordPress sites**, the **bulk of the market’s revenue** is captured by premium providers such as **WP Engine and Automattic**. - **Merlin’s Insight**: The **revenue disparity** suggests that companies like GoDaddy focus on high-volume, low-cost hosting rather than pursuing higher-value WordPress solutions. --- ### 6. **Merlin’s Observations on GoDaddy and WordPress Hosting Quality** - **[977:48 - 985:76]** - **Community Sentiment**: - GoDaddy, along with other budget hosts, is **not regarded highly** by the WordPress community. - Merlin references **community complaints**, indicating that users have **had negative experiences** with GoDaddy-hosted WordPress sites, suggesting **performance and usability issues**. --- ### 7. **GoDaddy in the Context of Automattic’s Control and License Agreements** - **[857:75 - 865:00]** - **License Agreements**: - Like other large hosts, **GoDaddy uses the WordPress brand** in its hosting offerings, possibly under **a licensing arrangement with Automattic**. - Merlin highlights this as a **point of tension**, reflecting **Automattic’s power over commercial usage of the WordPress name**, which likely affects GoDaddy’s operations and marketing strategies. --- ### 8. **GoDaddy’s Lack of Significant Contribution to 'Five for the Future'** - **[1505:92 - 1527:40]** - **Automattic's Frustration**: - Matt’s complaints extend to hosting providers like **GoDaddy**, which he believes **do not meet the 5% contribution benchmark** he set for companies profiting from WordPress. - **Comparison**: Matt compares Automattic’s extensive contributions to the **minimal involvement** from providers like GoDaddy and WP Engine, adding to his grievances. --- ### 9. **GoDaddy as Part of the Fragmented Hosting Ecosystem** - **[1261:48 - 1281:88]** - **Fragmentation Insight**: - Merlin mentions that GoDaddy is part of the **fragmented hosting ecosystem**, which includes a mix of **premium hosts like WP Engine** and **low-cost providers like GoDaddy**. - **Observation**: This fragmentation complicates Automattic’s efforts to control the hosting landscape and **enforce community contributions**. --- ### 10. **Community Sentiment toward GoDaddy** - **[974:63 - 985:76]** - **Negative Reputation**: - Many WordPress users in the community express **dissatisfaction with GoDaddy’s hosting services**. - **Merlin’s Take**: He hints that users prefer **premium alternatives** due to **GoDaddy’s perceived performance limitations**, reinforcing the company's **budget-hosting reputation**. ### Summary of GoDaddy's Role: - **Conflict with Matt Mullenweg**: Stemmed from Matt’s belief that GoDaddy **benefits from WordPress without adequate contributions**. - **Licensing Agreement**: Suggests **GoDaddy may pay fees to Automattic** for the use of the WordPress brand in marketing. - **Performance Issues**: GoDaddy is **not favorably viewed** by the community, with many users preferring premium hosting providers. - **Fragmented Market Position**: GoDaddy **hosts many WordPress sites**, but its business model focuses more on **low-cost, high-volume hosting**. ## 🗣️ Paraphrase: 1. "Matt holds a deep grudge against WP Engine, believing they benefit unfairly from WordPress without contributing proportionately." → Mullenweg feels that WP Engine's financial success comes at the expense of Automattic’s efforts, causing tension over unpaid contributions. 2. "The WordPress trademark is owned by the Foundation but licensed commercially to Automattic." → Although the Foundation holds the trademark, Automattic retains exclusive rights to monetize it through licensing. ## 📰 Newsletter: 📰 **Community Buzz**: This week’s newsletter dives into the latest WordPress drama! 🚀 The ongoing conflict between Matt Mullenweg’s Automattic and WP Engine sheds light on the tensions in open source projects. Matt’s push for companies to give back 5% of their time is under scrutiny, and licensing issues have resurfaced. What does this mean for the future of WordPress hosting and plugins? Stay tuned for insights, as well as recent updates from the WordPress ecosystem. Check out the full story [here](https://www.youtube.com/watch?v=XSb4Lul0qlc)! ## ✅ Action Items: - Align the article with my focus on open-source advocacy. - Examine Automattic’s "Five for the Future" initiative and its influence on community engagement. - Reflect on how these conflicts shape sustainable funding strategies. ## 🧪 Hypotheses: - **H1**: Automattic's licensing approach could discourage external contributions. - **H2**: Hosting companies may diverge from WordPress in favor of independent ecosystems. ## 📊 Methodology: - Surveys among WordPress hosting providers to assess their compliance with the 5% rule. - Analysis of financial reports to identify profitability trends in hosting companies. ## ❓ Questions: 1. How does Automattic’s control impact the WordPress community? 2. Are Matt’s expectations realistic for non-Automattic companies? ## 🔮 Future Research: Explore alternatives to the "Five for the Future" initiative and potential shifts toward decentralized plugin registries. ## 💡 Implications: The future of WordPress may see increased friction if hosting providers move towards non-WordPress solutions. ## 🧠 Learning Styles Assessment: - **Visual**: Limited diagrams or visual aids. - **Verbal**: Strong focus on storytelling but lacks detailed technical examples. - **Logical**: Arguments are clear but some sections meander. - **Social**: Could benefit from community engagement prompts. ## 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Unknown. - **Keyboard Navigation**: Not applicable as it's a transcript. - **Contrast and Readability**: Text formatting may need improvement for clarity. ## 🌍 DEIB Assessment: - **Representation**: Needs more diversity in viewpoints. - **Inclusive Language**: The language is colloquial and may alienate non-native speakers. ## ✅ Logical validity: - **Positive Reasoning**: The narrative explores legitimate conflicts in open-source projects. - **Logical Fallacy**: Some arguments rely on personal grudges, undermining objectivity. ## 🔍 SEO Evaluation: - **Keywords**: Effective use of "WordPress drama", "Matt Mullenweg", "GPL licensing". - **Title Tag**: Relevant but could include "conflict" for better SEO. ## 🎯 Conclusion: The WordPress drama reflects the challenges of maintaining open-source ecosystems, balancing commercial interests with community expectations. As hosting companies grow, their relationship with Automattic will likely remain strained without clear boundaries. Short Summary for [I tried to explain the whole Wordpress drama](https://www.youtube.com/watch?v=XSb4Lul0qlc) by [Merlin](https://merlin.foyer.work/) YouTube Video Title: Explaining the Wordpress Drama with a Tech Expert [00:05](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=5) Wordpress drama involves billionaires and company disputes [02:10](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=130) Wordpress drama and its origins. [06:18](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=378) Wordpress.com, wordpress.org, and WordPress Foundation have complex relationships and licensing issues. [08:32](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=512) The Wordpress drama raises questions about the foundation's actions. [12:39](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=759) Protecting PHP code was difficult, unlike HTML and JavaScript [14:33](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=873) WordPress should contribute 5% of engineering time or revenue to WordPress back for growth. [18:25](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1105) WP Engine's impact on WordPress ecosystem [20:17](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1217) WP engine holds a significant share of the WordPress hosting market [24:19](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1459) Conflict between Wordpress.org and automatic [25:52](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1552) Challenges with open-source projects and licensing [29:23](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1763) The importance of open source in technology [31:05](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1865) Jealousy over benefitting off WordPress work [34:58](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2098) WordPress drama: Demanding 8% revenue [36:58](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2218) Wordpress drama surrounding the commercial side of the business [40:49](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2449) Concerns raised about lack of contribution to WordPress [42:31](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2551) Wordpress.com sucks due to lack of focus on hosting platform [46:35](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2795) WordPress drama around WP GraphQL and WP Engine [48:21](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2901) Employee departures at Automattic due to WordPress drama. [52:01](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3121) WP Engine's actions and conflict with WordPress community [53:44](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3224) Anticipated outcomes of the WordPress drama [56:54](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3414) WordPress drama and licensing issues [58:32](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3512) Wordpress drama involves jobs and careers at stake. --------------------------------- Detailed Summary for [I tried to explain the whole Wordpress drama](https://www.youtube.com/watch?v=XSb4Lul0qlc) by [Merlin](https://merlin.foyer.work/) YouTube Video Title: Explaining the Wordpress Drama with a Tech Expert [00:05](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=5) Wordpress drama involves billionaires and company disputes - The drama is complex and involves competing billionaires acting like a startup with very few employees. - Dan, a guest, provides insights into the intricacies and history of the drama. [02:10](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=130) Wordpress drama and its origins. - The speaker has a history with Wordpress dating back to its early days as Cafe Press and B2. - The speaker is intrigued by the current drama surrounding Wordpress and wants to know more about it. [06:18](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=378) Wordpress.com, wordpress.org, and WordPress Foundation have complex relationships and licensing issues. - Wordpress.com is a for-profit enterprise that hosts Wordpress websites and handles domain registration. - Wordpress.org maintains the open-source code of Wordpress, but the trademark is owned by the Wordpress Foundation, with exclusive commercial licensing granted to automatic. [08:32](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=512) The Wordpress drama raises questions about the foundation's actions. - The foundation's actions are being questioned in terms of public benefit and adherence to its charter. - The drama has a history of conflict and controversy, such as Matt's issues with paid themes violating the GPL. [12:39](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=759) Protecting PHP code was difficult, unlike HTML and JavaScript - Matt spent over 100K on a domain to prevent the theme creator from having it - Matt engages in disputes with hosting providers like GoDaddy and Bluehost for WordPress usage [14:33](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=873) WordPress should contribute 5% of engineering time or revenue to WordPress back for growth. - WordPress project has around 80% code turnover every year, leading to constant rewriting and instability. - The wordpress.com hosting platform is considered one of the least viable options in the WordPress community. [18:25](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1105) WP Engine's impact on WordPress ecosystem - WP Engine has significant influence on popular WordPress plugins like ACF and WP graphql. - They focus on how WordPress is being consumed and have seen rapid growth as a hosting provider. [20:17](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1217) WP engine holds a significant share of the WordPress hosting market - WP engine revenue is around $400 million a year - WP engine is larger than wordpress.com in market share [24:19](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1459) Conflict between Wordpress.org and automatic - Matt felt that another company was making too much money off of Wordpress and not giving back to automatic and wordpress.org - Matt compared the amount of engineering time spent on WordPress by automatic and WP engine, and felt it was unfair [25:52](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1552) Challenges with open-source projects and licensing - Discussion on challenges faced by companies like Drupal and WordPress due to massive rewrites - Issues highlighted with the drama between Elastic search and AWS regarding licensing and contributions [29:23](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1763) The importance of open source in technology - Open source contributors are often underappreciated despite their valuable work - The vocal minority of open source contributors can sometimes overshadow the majority of dedicated individuals [31:05](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=1865) Jealousy over benefitting off WordPress work - Matt feels WP engine unfairly benefits from his work on WordPress - Proposes forking system to create competitive alternatives [34:58](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2098) WordPress drama: Demanding 8% revenue - CEO requests 8% revenue as trademark licensing fee. - CEO goes nuclear on stage calling out WP engine as a cancer. [36:58](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2218) Wordpress drama surrounding the commercial side of the business - The founder expresses discontent over the disparity in profit with WP Engine. - WP Engine retaliates with a cease and desist after being labeled as 'cancer' in the ecosystem. [40:49](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2449) Concerns raised about lack of contribution to WordPress - Hosts being questioned for not contributing enough back to WordPress community - Founder using trademark retaliation for perceived ethical violation [42:31](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2551) Wordpress.com sucks due to lack of focus on hosting platform - Automatics devs spend significant time on maintaining Wordpress code - Majority of Wordpress code comes from Automatic employees [46:35](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2795) WordPress drama around WP GraphQL and WP Engine - WordPress founder Matt trying to poach WP Engine developer for WP GraphQL - Open source developer considering move to private Equity company for more security and potential higher pay [48:21](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=2901) Employee departures at Automattic due to WordPress drama. - Employee wanted best for plugin but disagreed with current direction. - Executive director of wordpress.org left amidst chaos and potential replacement. [52:01](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3121) WP Engine's actions and conflict with WordPress community - WP Engine's actions regarding filtering RSS feed and blocking access highlighted by the community. - Significant conflict between WP Engine and WordPress community regarding trademark violations. [53:44](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3224) Anticipated outcomes of the WordPress drama - Prediction of a settlement and advice for Matt to tone down - Foresee splitting into two WordPress versions: one stable, one innovative [56:54](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3414) WordPress drama and licensing issues - WordPress Foundation's licensing restrictions and need for contributions - Considerations for a radical shift in direction for WordPress.com and Open Press [58:32](https://www.youtube.com/watch?v=XSb4Lul0qlc&t=3512) Wordpress drama involves jobs and careers at stake. - Company executive's autocratic behavior towards communication is criticized. - Investors are also accountable for the situation. <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/I Tried to Explain the Whole Wordpress Drama|I Tried to Explain the Whole Wordpress Drama, Theo Throwaways]] ## Highlights - spat with GoDaddy I don't know much in ([View Highlight](https://read.readwise.io/read/01ja88smdzr6cwvvy7y7yrxy3m))