What Makes Open Source Work: Licensing and Beyond

Is your favorite open source project truly open? A license change can create vendor lock-in. Learn the critical signs to look for beyond OSI approval.

#1about 2 minutes

Defining open source software beyond the license

Open source is typically defined by its OSI-approved license, but this legal definition alone may not capture the full value of a project.

#2about 6 minutes

Understanding the diverse stakeholders in open source

The open source ecosystem involves lawyers, commercial investors, contributors, and end-users, each with different motivations and perspectives on what makes a project work.

#3about 2 minutes

Why end users choose to adopt open source software

Users are drawn to open source software because it offers a lower total cost of ownership, a competitive ecosystem of vendors, and the freedom to customize solutions.

#4about 4 minutes

Why an open source license is necessary but not sufficient

A valid license is essential but doesn't guarantee a project is usable or healthy, as commercial interests can lead to degradation that harms the user experience.

#5about 3 minutes

Evaluating projects using the organic software model

Simon Phipps' "organic software" concept provides a scorecard for assessing project health based on governance, roadmaps, and the ability to fork, as seen with OpenTofu and Valkey.

#6about 4 minutes

A practical checklist for assessing open source projects

Key criteria for evaluating a project's long-term viability include its governance model, public development process, community health, vendor ecosystem, and security maintenance.

#7about 3 minutes

The central role of community-centric governance

A project's core incentive structure, specifically whether it is governed by and for the community, is the most important predictor of its long-term health and user-friendliness.