Response to DHH  ## Metadata - Author: [[Matt]] - Full Title: Response to DHH - Category: #articles - Document Note: --- tags: [#OpenSource, #WordPress, #SoftwareDebate] - #MattMullenweg - #DHH - #Automattic Author: Matt Mullenweg Source: Matt's Blog Reference: [Matt Mullenweg's response to DHH](https://ma.tt/2024/10/on-dhh/) date created: 2024-10-14 16:05 --- # Title: Matt Mullenweg's Response to DHH ## 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) ## 📝 Summary: Matt Mullenweg addresses criticism from David Heinemeier Hansson (DHH), defending Automattic’s approach to open source and trademarks. He challenges DHH’s take on scaling businesses, open source practices, and Automattic's contributions versus 37signals. ## 📖 Main Content: Mullenweg argues that Automattic contributes significantly to open-source projects compared to 37signals and addresses the topic of trademark usage within the open-source community. He draws attention to inconsistencies in DHH’s criticism and highlights Automattic’s sustainability in growing revenue and community contributions. ### 🗒️ Notes - **Automattic's Contribution**: 6.58M lines of open-source code versus 143K from 37signals. - **Trademark Use**: Addresses WP Engine's alleged trademark abuse while pointing out Rails’ own trademark policies. - **Scalability Critique**: Suggests DHH’s projects struggle to scale beyond niche markets. - **Community Feedback**: Mullenweg invites more diverse contributions to WordPress. ## 📖 References: - [Matt Mullenweg's Blog](https://ma.tt/2024/10/on-dhh/) ## 🗣️ Paraphrase: 1. Matt notes that Automattic’s open-source contributions far exceed those of 37signals, challenging DHH's criticism of Automattic’s practices. 2. He criticizes DHH’s inconsistency in defending WP Engine’s trademark misuse while maintaining strict control over Rails’ trademark. ## 📰 Newsletter: **Open Source Insights – Latest from the WordPress Ecosystem!** Matt Mullenweg defends Automattic's open-source strategy amidst critiques from 37signals co-founder DHH. Matt emphasizes the importance of trademarks and scalability in sustaining open-source projects. Learn more about Automattic’s latest contributions, plugin updates, and how the WordPress community is growing stronger! Full story [here](https://ma.tt/2024/10/on-dhh/). ## ✅ Action Items: 1. **Aligning with Advocacy**: Matt’s response supports transparency in trademark policies—relevant to open-source program office (OSPO) goals. 2. **Educational Value**: Explains trademark complexities, enhancing understanding for future contributors. 3. **Community Growth**: Stresses the need for diverse contributors, aligning with your advocacy for onboarding new contributors. ## 🧪 Hypotheses: 1. **Trademark Policies’ Impact**: How does trademark enforcement affect open-source community engagement? 2. **Scaling and Contribution Balance**: Investigate if revenue models influence open-source contributions. ### 📊 Methodology: - **Data Collection**: Analyze contribution trends and trademark disputes. - **Design**: Comparative case studies of Automattic and 37signals. ### ❓ Questions: - How do companies balance trademark protections with open-source values? - What models support sustainable growth in open-source businesses? ### 🔮 Future Research: Explore how trademark governance impacts community trust in open-source ecosystems. ### 💡 Implications: Clear trademark policies could shape future contributions and create sustainable ecosystems. ### 🧠 Learning Styles Assessment: 1. **Visual Learners**: Add diagrams explaining trademark processes. 2. **Aural Learners**: Include podcast links about open-source governance. 3. **Verbal Learners**: Add case studies for deeper exploration. 4. **Kinesthetic Learners**: Provide exercises on navigating trademark issues. ### 📊 Accessibility Assessment: - **Screen Reader Compatibility**: Ensure alt text for embedded images. - **Keyboard Navigation**: Verify all interactive content supports keyboard users. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - **Inclusive Language**: Simplify technical jargon for broader accessibility. - **Representation**: Incorporate case studies from various cultural perspectives. ### ✅ Logical validity: - **Sound Reasoning**: Mullenweg’s critique of trademark inconsistencies is well-supported. - **Fallacy Detected**: Possible **ad hominem** regarding DHH's personal traits undermines the objectivity. ### 🔍 SEO Evaluation: 1. **Keywords**: "Open Source," "Trademark Policy," "WordPress Community." 2. **Meta Description**: Use: “Matt Mullenweg defends Automattic’s trademark strategy in response to DHH’s critique.” 3. **Internal Links**: Link related articles on open-source trademarks. 4. **Image Optimization**: Add descriptive alt text for images to improve accessibility and SEO. ## 🎯 Conclusion: Matt Mullenweg’s response defends Automattic’s open-source and trademark practices while calling for transparency and scalability in the broader ecosystem. His insights emphasize the importance of aligning business models with sustainable community growth. - Document Tags: [[dhh]] [[Matt Mullenweg]] [[open source]] [[open source corporate contribution]] [[wordpress]] [[wpdrama]] [[wp engine]] - Summary: I’ll just remind everyone at the start that this a respectful debate, and DHH and I tried to get on a call but couldn’t because we were both traveling. However, “Automattic is do… - URL: https://ma.tt/2024/10/on-dhh/ I’ll just remind everyone at the start that this a respectful debate, and DHH and I tried to get on a call but couldn’t because we were both traveling. However, “[Automattic is doing open source dirty](https://world.hey.com/dhh/automattic-is-doing-open-source-dirty-b95cf128)” is an abomination of a headline, and David’s second post [Open source royalty and mad kings](https://world.hey.com/dhh/open-source-royalty-and-mad-kings-a8f79d16), is just sloppy. So I’m forced to reply publicly: DHH claims to be an expert on open source, but his toxic personality and inability to scale teams means that although he has invented about half a trillion dollars worth of good ideas, most of the value has been captured by others. Let’s look at 37signals portfolio: * [Hey](https://www.hey.com/), proprietary, some sort of email / calendar / blogging thing that almost no one uses. It’s trying to be Gmail/Workspace and [Medium](https://medium.com/) at the same time. And you can arbitrarily cut off anyone publishing with Hey, they have no open source rights. * [Campfire](https://once.com/campfire), proprietary, you invented [Slack](https://slack.com/) but they took the idea and built a $900M/ARR business with it, while you are trying to make shrinkwrap licensing a “thing” with [Once](https://once.com/). * [Writebook](https://once.com/writebook), proprietary. Pretty cool. * [Basecamp](https://basecamp.com/), proprietary. Great software. You invented the ideas [Atlassian](https://www.atlassian.com/) ran with and built a $4.4B/revenue and growing business. * [Rails](https://rubyonrails.org/), finally some open source! Looks like ~943k lines of code, 143k from Basecamp org. Automattic publishes 6.58M lines of open source code, 6.9x more than you. Yet, we’re “doing open source dirty”? [Shopify](https://www.shopify.com/) used Rails to build a $7B/revenue and growing business, why didn’t you? David, perhaps it would be good to explore with a therapist or coach why you keep having these great ideas but cannot scale them beyond a handful of niche customers. I will give full credit and respect. 37signals inspired tons of what Automattic does! We’re now half a billion in revenue. Why are you still so small? I was surprised someone as smart as DHH would fall for WP Engine’s lame deferral to make this about “GPL code” or forking, rather than trademarks. We have no problem with their use of GPL code, our beef is with their trademark abuse. Let’s talk about trademarks! I don’t own the WordPress trademark personally, it belongs to a foundation on which I’m one of three votes. Rails? > **“Rails”**, **“Ruby on Rails”**, and the **Rails logo** are registered trademarks of **David Heinemeier Hansson**, but are under exclusive license to [The Rails Foundation](https://rubyonrails.org/foundation), which is responsible for administering their use and permission. You may not use these trademarks in a commercial setting to imply that your product or service is endorsed or associated with Ruby on Rails without permission. You may use these marks to refer to Ruby on Rails in a way where it’s clear that you’re simply referring to the project, not claiming endorsement or association. > > Huh, sounds like if I wanted to start RailsEngine I would need a trademark license. You are ignoring WP Engine’s trademark abuse while retaining the same for your Rails trademark. The same as Drupal, where “Drupal is a registered trademark of Dries Buytaert, who retains sole ownership and control of this policy and any trademark licensing.” ([Dries has also decided to drop in on this debate](https://dri.es/solving-the-maker-taker-problem).) Dries or David could arbitrarily withdraw their trademarks from the foundations / etc. at any time and for any reason or no reason. If they die, it’s not clear what happens to the trademarks. Their communities should look into that and consider a different name or taking over the trademark into a Foundation with multiple board members. David, perhaps instead of spending [$2M on a race car](https://www.autoblog.com/news/pagani-zonda-hh-commissioner-revealed-as-30-year-old-chicago-sof), you should do some [philanthropy](https://ma.tt/2024/09/charitable-contributions/). Instead of [bragging about your beautiful office in the clouds](https://world.hey.com/dhh/how-it-started-how-it-s-going-baefaf09), you should question why you can’t scale teams. When you did a (less generous) buy-out offer [33% of your team left](https://www.theverge.com/2021/4/30/22412714/basecamp-employees-memo-policy-hansson-fried-controversy), vs [8.4% of mine](https://ma.tt/2024/10/alignment/). I’m unsure why you felt you had to insert yourself into this fight with Silver Lake / WP Engine and take their side, but here we are. Respectfully,, Response to DHH, Matt, 01ja642657rer30b7p1j1yzqh0.