A program can be freely available while depending on a handful of people who understand how to maintain it. Open-source software begins with permissions to use, inspect, modify, and redistribute code, but an ecosystem includes the relationships that keep useful work happening around it.

The license defines important freedoms. It does not decide which changes the main project accepts, who responds to failures, or who pays for maintenance. Users, volunteers, employers, foundations, and commercial services can all depend on the same project while having different priorities.

Availability is not the same as stewardship

Someone still has to review contributions, explain decisions, maintain compatibility, and help newcomers become capable contributors. Governance arrangements determine how that responsibility is distributed and what happens when people disagree.

A company can benefit greatly from shared work while contributing little to its upkeep. A volunteer maintainer can acquire substantial influence without receiving enough support to continue. Forking offers an exit when code can be copied, but rebuilding relationships and trust is much harder than copying files.

The ecosystem becomes more understandable when its different layers are separated: legal permissions, practical authority, technical knowledge, money, and the community’s expectations. Openness at one layer does not guarantee openness or sustainability at the others.

Real cases