Open Source Software Developers Are SELLOUTS!

YouTube Video

Summary

This YouTube video transcript discusses the recent announcements from the maintainers of popular .NET open-source packages - AutoMapper, Mediator, and MassTransit - regarding their transition to a commercial model. The speaker addresses a viewer’s question about the implications of this shift, both for these specific packages and the broader open-source ecosystem.

The speaker starts by acknowledging the user’s question and identifying the packages in question, explaining their popularity among .NET developers. He mentions Jimmy Bogart as the maintainer of AutoMapper and Mediator and Chris Patterson (fatboy G) as the maintainer of MassTransit. He notes the community’s reaction, which includes concern and worry about the future of these previously free and open-source tools.

From a maintainer’s perspective, the speaker focuses on Jimmy Bogart’s blog post explaining the decision. He highlights the point that maintaining such large and widely used open-source projects is a full-time job. Bogart’s commit history is cited as evidence, showing a significant drop in contributions after he moved away from a sponsored environment where open-source work was part of his job. The speaker empathizes with maintainers facing burnout and lack of time, suggesting commercialization as a way to secure resources and revitalize project development and maintenance. He counters the idea that this is abandonment, viewing it as an attempt to provide necessary TLC to the projects. He also addresses a comment suggesting many contributors carried these projects, clarifying that in reality, a small number of individuals bear the brunt of the maintenance work.

Switching to the case of MassTransit, the speaker reviews Chris Patterson’s announcement about version 9 becoming commercial. He notes that MassTransit V8 will remain open source and supported with security patches for a transition period until 2026. V9, however, will be a subscription-based commercial product with different pricing tiers for small/medium businesses and large organizations (starting at $400/month for SMBs and $1200/month for large orgs). The speaker expresses personal reservations about the pricing, especially as a small business or individual developer, finding the cost prohibitive and suggesting he might stick with V8. He acknowledges that while the pricing is steep for individuals and small teams, it might be reasonable for larger enterprises. He interprets MassTransit’s move as a clear shift to a business model, which he believes is their right but might alienate some users.

From a consumer’s perspective, the speaker reflects on the common reaction of “you get what you deserve for not writing your own stuff.” He argues against this extreme view, stating that building everything from scratch is often impractical and slows down development. He advocates for a balanced approach, suggesting the use of “shim layers” or abstraction layers around third-party libraries. This strategy allows for easier swapping of libraries if needed in the future, mitigating the impact of changes like commercialization. He shares his personal coding practices, including using abstractions for most third-party libraries (like Dapper) but less so for core Microsoft interfaces (like ILogger). He clarifies he’s not against using NuGet packages but emphasizes thoughtful integration and potential isolation through abstractions.

Regarding the future of open source, the speaker believes that more projects might move towards commercial models, especially support-based licensing, to ensure sustainability for maintainers who dedicate significant time to these projects. He acknowledges philosophical objections to commercializing open source but highlights the practical realities of maintaining large projects and the need for compensation for maintainers’ efforts. He concludes by encouraging viewers to contribute back to open-source projects to support their longevity and lessen the burden on maintainers. He reiterates that while he dislikes some aspects of these commercial transitions (like MassTransit’s pricing for small businesses), he respects the maintainers’ choices and sees it as a potentially necessary evolution for some open-source projects.

Accuracy

The information provided in the transcript is generally accurate in regards to established knowledge about open source and the specific packages mentioned.

• Commercialization of Open Source: The speaker accurately describes the trend of some open-source projects moving towards commercial models. This is a recognized phenomenon driven by the need for sustainable funding and resources for project maintenance and development.
• Maintainer Burnout and Sustainability: The reasons given for commercialization, such as maintainer burnout, lack of time and resources, and the desire to provide better support and accelerate development, are valid and commonly cited in discussions about open-source sustainability.
• Open Source Licensing and Forking: The speaker correctly points out that the existing open-source codebases of AutoMapper, Mediator, and MassTransit remain open source and can be forked. This aligns with the principles of open-source licensing, allowing users to continue using and modifying the software even if the original project transitions to a commercial model.
• Community Reactions: The transcript accurately portrays the mixed reactions within the open-source community to such announcements. Concerns about pricing, the perceived shift away from the “free” nature of open source, and the implications for existing users are typical responses.
• Abstraction Layers as a Mitigation Strategy: The advice to use abstraction layers or shim layers when integrating third-party libraries is a well-known and recommended software engineering practice. It enhances flexibility and reduces dependency on specific implementations, making systems more adaptable to changes in external libraries.
• Specific Package Details: The information about AutoMapper, Mediator (maintained by Jimmy Bogart), and MassTransit (maintained by Chris Patterson aka fatboy G) and their respective announcements about commercialization is consistent with publicly available information at the time of the video’s likely recording (early April 2024, based on the April Fool’s joke reference). The pricing details mentioned for MassTransit V9 also align with the information released by the MassTransit team.

Minor Nuances and Considerations:

• “Philosophical” Opposition to Commercialization: While the speaker mentions philosophical opposition to commercializing open source, the spectrum of views within the open-source community is broad. Many in the community understand and even support sustainable business models for open source, as long as they align with open-source values and don’t overly restrict access or freedom. The focus is often on ensuring the “openness” aspect is preserved in some form, even with commercial elements.
• Complexity of Open Source Business Models: The video simplifies the discussion to moving “to a commercial model.” In reality, there are various open-source business models (support, dual-licensing, open core, hosted services, etc.). The transcript touches upon support models but doesn’t delve into the nuances of each model.
• Impact on Community Contributions: The transition to commercial models can sometimes impact community contributions. While it can free up maintainers to focus on core development, it might also reduce community involvement if the commercial entity becomes more controlling of the project’s direction or contribution process. This is a complex dynamic not fully explored in the transcript but is a relevant aspect of such transitions.

Overall, the transcript provides an accurate and insightful commentary on the discussed topic, reflecting a good understanding of open-source principles and the practical challenges and considerations surrounding commercialization in the open-source world.

Resources

Here are the top 5 most relevant resources to learn more about the subject presented in the transcript:

1. Jimmy Bogart’s Blog (jimmybogard.com): This is the primary source for understanding the reasoning behind AutoMapper and Mediator’s transition. Searching for “AutoMapper commercial” or “Mediator commercial” on his blog will likely lead to the specific blog post discussed in the video, offering a first-hand perspective from the maintainer.

   • Relevance: Direct insight into the maintainer’s perspective for two of the mentioned packages.
   • Type: Blog, Primary Source.

2. MassTransit Official Website (masstransit-project.com or masstransit.io): This is the official website for MassTransit. Look for the “Version 9 Announcement” or search for “MassTransit commercial” to find the official announcement regarding their commercial model and pricing.

   • Relevance: Direct insight into MassTransit’s commercialization strategy and details.
   • Type: Project Website, Official Announcement.

3. “The Cathedral and the Bazaar” by Eric S. Raymond (http://www.catb.org/~esr/writings/cathedral-bazaar/): This classic essay provides foundational understanding of open-source development models and philosophies. While it doesn’t directly address commercialization, it lays the groundwork for understanding the open-source community and its values, which is crucial for contextualizing the commercialization discussion.

   • Relevance: Foundational understanding of open-source principles and development.
   • Type: Essay, Foundational Text.

4. “Producing Open Source Software” by Karl Fogel (https://producingoss.com/): This book is a comprehensive guide to the practical aspects of developing and managing open-source projects. It covers topics like licensing, community building, and sustainability, providing a broader context for the challenges faced by open-source maintainers and potential solutions, including business models.

   • Relevance: Practical guide to open-source development and sustainability.
   • Type: Book, Practical Guide.

5. “Open Source Business Models” - various articles and resources (search terms: “open source business models”, “sustainable open source”): A broad search on this topic will yield numerous articles, blog posts, and guides discussing different business models for open-source software. This will provide a wider perspective on the various approaches projects can take to achieve sustainability, beyond just moving to a fully commercial model. Look for resources from organizations like the Open Source Initiative (OSI) or the Software Freedom Conservancy.

   • Relevance: Understanding the range of business models available to open-source projects.
   • Type: Articles, Guides, Broad Overview.

These resources offer a combination of specific information about the mentioned packages and broader context about open-source software, its challenges, and potential paths to sustainability, helping anyone interested to delve deeper into the subject.