> Markdown version of [/videos/1416-what-makes-open-source-work-licensing-and-beyond](https://www.wearedevelopers.com/videos/1416-what-makes-open-source-work-licensing-and-beyond). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# What Makes Open Source Work: Licensing and Beyond

When commercial interests clashed with open source ideals, giants like Redis and HashiCorp changed their licenses. Discover why true open source survival now demands independent foundation governance.

- **Speakers:** [Peter Zaitsev](https://www.wearedevelopers.com/@peter-zaitsev)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 25:00
- **URL:** https://www.wearedevelopers.com/videos/1416-what-makes-open-source-work-licensing-and-beyond

## Summary

The definition of open source software extends far beyond the traditional Open Source Initiative (OSI) license or simple GitHub repository access. While early "romantic" open source projects like Linux were built by developers primarily for the joy of creation, today's open source ecosystem is heavily influenced by massive commercial interests. This shift has introduced a growing tension between investors seeking vendor lock-in and the community contributors and end users who rely on an open ecosystem. Consequently, evaluating an open source tool requires looking past licensing to understand its underlying governance and financial incentives.

Recent ecosystem disruptions—such as Elastic, Redis, and HashiCorp changing their licenses—highlight the risks of single-vendor control, which often triggers community forks like Valkey and opentofu. As profit motives continuously risk the "enshittification" of popular technologies, enterprise users must identify the true indicators of a healthy open source project. A secure, mature project requires robust governance managed by an independent foundation rather than a single corporate entity. It also necessitates a public development model that actively accepts community contributions, straightforward accessibility to binaries, dedicated security maintenance, and a diverse vendor ecosystem to prevent monopoly control.

Currently, platforms like GitHub identify project licenses but lack mechanisms for scoring broader aspects of community health, track records, and operational transparency. To safeguard the future of the ecosystem, the industry needs standardized, crowdsourced scorecards developed by independent nonprofits. Ultimately, the most reliable and practically usable open source software resolves back to a core principle: the project must be actively governed by the community, for the community, ensuring robust roadmaps and enduring user choice.

**Keywords:** open source licensing, OSI definition, commercial open source software, vendor lock-in risks, community governance models, software enshittification, open source forks, opentofu, valkey, independent software foundations, public development methodologies, open source security maintenance, open source scorecards, enterprise database customization, total cost of ownership

## Chapters

1. **Standard definitions of open source and free software** (00:11) — Standard definitions of open source software demonstrate why mere source code access is insufficient for true usability.
1. **Stakeholder perspectives on evolving open source models** (03:01) — Commercial investors and open source developers prioritize different leverage points compared to early grassroots collaboration efforts.
1. **The shift toward end-user open source software** (06:41) — Open source has evolved from specialized developer tooling to accessible mainstream applications driven by lower costs and advanced customization.
1. **Why an open source license is fundamentally insufficient** (11:15) — Open source licenses fail to guarantee ecosystem health when restrictive build instructions and aggressive monetization compromise the underlying user experience.
1. **Scorecards and open source project governance models** (15:03) — Frameworks for evaluating governance models reveal why project forks become necessary when corporate interests conflict with broader community needs.
1. **Identifying viable and sustainable open source projects** (18:04) — Core requirements for sustainable open source adoption include independent foundation governance, public development models, vendor diversity, and proactive security maintenance.
1. **Prioritizing community governance for sustainable open source** (22:24) — Community-driven governance models and independent project scorecards remain the most reliable predictors of a healthy long-term software ecosystem.

## Related Moments

- [Balancing open source access with enterprise monetization](https://www.wearedevelopers.com/videos/1906-rag-s-not-dead-you-re-just-using-it-wrong-phil-nash) (from "RAG's Not Dead, You're Just Using It Wrong! - Phil Nash")
- [Achieving faster innovation and compliance with vendor-neutral open source](https://www.wearedevelopers.com/videos/1448-harnessing-the-power-of-open-source-s-newest-technologies) (from "Harnessing the Power of Open Source's Newest Technologies")
- [Increasing enterprise awareness of critical open source dependencies](https://www.wearedevelopers.com/videos/604-can-you-build-a-career-in-open-source) (from "Can you build a career in open source?")
- [Building viable economic models for open source operations](https://www.wearedevelopers.com/videos/100031-building-on-open-source-the-new-product-playbook) (from "Building on Open Source: The New Product Playbook")
- [The historical evolution from free software to open source](https://www.wearedevelopers.com/videos/1124-the-future-of-open-source) (from "The Future of Open Source")
- [Navigating license shifts and the commercial open source playbook](https://www.wearedevelopers.com/videos/100150-keeping-your-ai-software-supply-chains-sovereign-in-the-age-of-commercial-open-source) (from "Keeping Your AI Software Supply Chains Sovereign in the Age of Commercial Open Source")

## Related Articles

- [The Future of Open Source: A Deep Dive - Scott Chacon at WeAreDevelopers World Congress 2024](https://www.wearedevelopers.com/magazine/471-the-future-of-open-source-a-deep-dive-scott-chacon-at-wearedevelopers-world-congress-2024)
- [Navigating a Career in Open Source](https://www.wearedevelopers.com/magazine/573-navigating-a-career-in-open-source)
- [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)
- [5 GitHub Repos That Help You Ship and Show Your Work](https://www.wearedevelopers.com/magazine/694-5-github-repos-that-help-you-ship-and-show-your-work)

## Related Jobs

- [Senior Open Source Advisor](https://www.wearedevelopers.com/jobs/ext/1278113-senior-open-source-advisor) at **ZEISS Group**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub**
- [Principal Software Engineer, Identity](https://www.wearedevelopers.com/jobs/ext/1469181-principal-software-engineer-identity) at **GitHub**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub**