Automattic / WP Engine Term Sheet  ## Metadata - Author: [[Automattic]] - Full Title: Automattic / WP Engine Term Sheet - Category: #articles - Document Note: --- tags: [#WordPress, #Automattic, #OpenSourceCommunity] - #WordPress - #Automattic - #OpenSourceCommunity Author: Automattic Source: Automattic Blog Reference: [https://automattic.com/2024/10/01/wpe-terms/](https://automattic.com/2024/10/01/wpe-terms/) date created: 2024-10-01 17:00 --- # Title: Automattic's Statement on WP Engine Terms ## Table of Contents:  - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ 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 (Diversity, Equity, Inclusion, and Belonging) Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: - [Automattic Blog: WP Engine Terms](https://automattic.com/2024/10/01/wpe-terms/) ## 📝 Summary: Automattic responds to recent controversies involving WP Engine by discussing the ongoing issues around trademarks, community engagement, and Automattic's role in the WordPress ecosystem. The statement highlights Automattic's commitment to supporting open source while navigating the complexities of trademark usage within the community. The post aims to clarify misunderstandings about trademark ownership and to ensure that Automattic’s actions align with the values of transparency and community involvement. ## 📖 Main Content: Automattic begins by acknowledging the ongoing debate over WP Engine's use of WordPress-related trademarks. Automattic asserts that they are striving to protect the WordPress brand while balancing the need for broad community engagement. The blog post mentions the importance of open source and clarifies that Automattic’s actions are rooted in preserving the integrity of the WordPress ecosystem, not in generating profit or excluding participants. The response further touches on how WP Engine’s use of the WordPress trademark potentially conflicts with established guidelines for trademark use under the WordPress Foundation. Automattic emphasizes that they are committed to working collaboratively with all contributors and stakeholders while upholding the rules that maintain the WordPress community's identity and purpose. ### 🗒️ Notes: - **Trademark Concerns**: - Automattic is concerned about WP Engine's usage of WordPress trademarks. - They emphasize protecting the brand for consistency across the community. - **Commitment to Community**: - Automattic wants to ensure transparency and fairness while enforcing trademark guidelines. - They stress the importance of open-source values and their commitment to not excluding contributors. - **Collaboration and Compliance**: - Automattic reiterates their willingness to collaborate with WP Engine. - They clarify that their actions are in line with community guidelines to preserve WordPress's mission. ## 📖 References: - [Automattic Blog: WP Engine Terms](https://automattic.com/2024/10/01/wpe-terms/) ## 🗣️ Paraphrase:  1. **Original**: "Automattic remains steadfast in its dedication to fostering an open and inclusive community while ensuring that our trademark guidelines are respected." - **Paraphrased**: Automattic is committed to maintaining an inclusive community, emphasizing adherence to trademark guidelines. 2. **Original**: "We aim to protect the WordPress brand's integrity, ensuring it is used consistently across the community without undermining the open-source values that we cherish." - **Paraphrased**: Our goal is to safeguard the integrity of the WordPress brand, ensuring consistent use while upholding open-source principles. ## 📰 Newsletter: 🚀 **Community Spotlight: Navigating Trademark Guidelines with Automattic** In response to the recent dispute between WP Engine and Automattic, Automattic has clarified its stance on trademark usage and community guidelines. Their focus remains on protecting the integrity of the WordPress brand and ensuring fair use across the community. Automattic emphasizes their commitment to transparency and collaboration, reminding us all of the values that make open source work. Interested in the full story and Automattic’s perspective? [Read more here](https://automattic.com/2024/10/01/wpe-terms/). ## ✅ Action Items: - **Aligning Open Source Advocacy**: This statement shows how trademark use is governed to protect community values. Highlighting the balance between protecting brand identity and fostering inclusivity aligns with my advocacy goals. - **Contributor Engagement**: Emphasize the importance of having clear guidelines for contributors to feel included without confusion over trademark use. - **Career Objectives**: Automattic’s approach to community engagement and transparency reflects the kind of leadership I want to foster as an OSPO director, focusing on inclusivity and fairness. ## 🧪 Hypotheses: 1. Consistent trademark enforcement contributes to a stronger brand identity within open-source communities. 2. Collaboration and transparency in decision-making improve community satisfaction and reduce conflicts. ### 📊 Methodology: - **Case Study Analysis**: Analyze other open-source projects with trademark disputes to determine the impact on community engagement. - **Surveys**: Conduct surveys within the WordPress community to understand how trademark enforcement affects contributor sentiment. ### ❓ Questions: - How can Automattic ensure trademark guidelines are fair without discouraging contributors? - What are the long-term impacts of trademark disputes on community participation? ### 🔮 Future Research: - Investigate the role of trademarks in open-source communities and their effects on brand consistency. - Explore alternative governance models that might balance trademark protection and community-driven innovation. ### 💡 Implications:  Future research could shape guidelines that both protect trademarks and encourage open-source contributions, providing a model for other open-source communities to follow. ### 🧠 Learning Styles Assessment: 1. **Visual Learners (Spatial)**: - **Present**: The article lacks diagrams or visual aids. - **Improve**: Add flowcharts or visual representations of the trademark enforcement process for better understanding. 2. **Aural Learners (Auditory-Musical)**: - **Present**: No auditory content available. - **Improve**: Consider providing an audio version of the blog post or embedding a related podcast. 3. **Verbal Learners (Linguistic)**: - **Present**: Rich in textual explanation. - **Improve**: Add storytelling elements or examples to illustrate the impact of trademark policies. 4. **Physical Learners (Kinesthetic)**: - **Present**: No hands-on components. - **Improve**: Include actionable steps for readers to engage with Automattic's guidelines. 5. **Logical Learners (Mathematical)**: - **Present**: The reasoning for trademark enforcement is explained. - **Improve**: Include statistics or a logical breakdown of past trademark conflicts and their resolutions. 6. **Social Learners (Interpersonal)**: - **Present**: Limited opportunities for community discussion. - **Improve**: Include a call to action for community feedback or discussion on the guidelines. 7. **Solitary Learners (Intrapersonal)**: - **Present**: The reflective tone can engage solitary learners. - **Improve**: Suggest readers consider how trademark protection affects their contributions. 8. **Naturalistic Learners**: - **Present**: No references to nature or environmental analogies. - **Improve**: Use analogies comparing community growth to ecosystems for better engagement. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: The blog post lacks proper alt-text for images. - **Improve**: Ensure all images have alt-text descriptions - Document Tags: [[matt mullenweg]] [[open source]] [[open source corporate contribution]] [[wordpress]] [[wpdrama]] [[wp engine]] - Summary: One of the many lies in Silver Lake and WP Engine’s C&D was their claim that Automattic demanded money from them moments before our CEO Matt Mullenweg gave his keynote at WordCamp US. Tha… - URL: https://automattic.com/2024/10/01/wpe-terms/ One of the many lies in [Silver Lake and WP Engine’s C&D](https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf) was their claim that Automattic demanded money from them moments before our [CEO Matt Mullenweg gave his keynote at WordCamp US](https://www.youtube.com/watch?v=fnI-QcVSwMU&t=149s). That is not true. Automattic asked for a verbal agreement that WPE would give some percentage of their revenue back into WordPress, either in the form of a trademark agreement or employee hours spent on core WordPress. For transparency, [Automattic is publishing the full term sheet](https://automattic.com/wp-content/uploads/2024/09/term-sheet-wp-engine-inc.-automattic-trademark-license_09.19.2024-1.pdf) WPE was offered on September 20th. Given WP Engine’s behavior, deception, and incompetence since September 20th these terms are no longer sufficient. Lee Wittlinger and Heather Brunner had ample time to resolve this conflict. In an effort to continue our transparency, here are some of the meetings we’ve had with WP Engine over the past 20 months: **February 2023** Feb 23: Matt Mullenweg (Automattic’s CEO), Heather Brunner (WP Engine’s CEO): Lunch in Houston at Eunice. **March 2023** Mar 21: [Matt and Matías (WP’s chief architect) speak at the WPE DE{CODE} conference](https://www.youtube.com/watch?v=kKHY6QPnclQ). **November 2023** Nov 28: Matt, Heather Brunner phone call. **January 2024** Jan 26: Matt, Heather Brunner Zoom call. Jan 28: Matt and Toni Schneider Zoom with Heather Brunner. Matt was [heading on sabbatical](https://ma.tt/2024/02/samattical/) and passing the torch to Toni to continue discussions as Automattic’s interim CEO. **February 2024** Feb 5: Toni Schneider and Heather Brunner discuss trademarks and commercial agreement. **March 2024** Mar 22: Meeting with Toni Schneider and Paul Maiorana from Automattic, Heather Brunner, Ezinne Udezue, Ramadass Prabhakar from WP Engine. Mar 29: WP Engine CEO Heather Brunner and Toni Schneider email on agreement terms. **May 2024** May 30: First term sheet shared with WP Engine via email. **June 2024** June 12: Zoom call with Steve Deckert from Automattic and Victor Yuan, Carl Hargraves, Ezinne Udezue, Ramadass Prabhakar from WP Engine. June 26: Steve Deckert follows up with Victor Yuan. Victor requests a call. **July 2024** July 3: 2nd terms review Zoom: Steve Deckert and Jesse Friedman from Automattic, Victor Yuan from WPE. July 16: Steve Deckert follows up with Victor Yuan expressing concern about timeline **September 2024** Sept 17: Mark Davies (Automattic CFO) / Lee Wittlinger (Silver Lake partner) Zoom Sept 19: Mark Davies (Automattic CFO) / Lee Wittlinger (Silver Lake partner) Zoom Sept 20: Mark Davies (Automattic CFO) / Lee Wittlinger (Silver Lake partner) Phone On September 19th and 20th, Lee and Heather did not answer any of Matt’s calls., Automattic / WP Engine Term Sheet, Automattic, 01j955a5xtv2pgw4bfqf8te343.