It started with a problem.
Richard Stallman announced the GNU Project in September 1983 with the goal of creating a free Unix-compatible operating system. In January 1984, Stallman quit his job at MIT and began writing GNU software. The Free Software Foundation's own account at gnu.org states: 'In January 1984 I quit my job at MIT and began writing GNU software.' In March 1985, Stallman published the GNU Manifesto and founded the Free Software Foundation to support the project. The GNU General Public License (GPL), first released in 1989, established the copyleft mechanism: software licensed under the GPL must remain freely available, and any derivative work must also be distributed under the GPL.
Historical sources below ↓Then something changed.
Open source changed the economics of software production. Software that many organizations needed — web servers, databases, programming languages — could be developed collaboratively by organizations that each benefited from the shared result without individually bearing the full cost. Apache, Linux, MySQL, and Python are examples of infrastructure software built on this model. Large companies contributed to open source projects because using shared infrastructure they helped improve was cheaper than building and maintaining equivalents alone. The model also changed developer careers: contributing to open source became a form of public portfolio, visible to potential employers.
What a builder can learn.
Our interpretation: open source demonstrated that competitive advantage does not always require exclusive possession. When infrastructure is shared, competition moves to services, customization, and support built on top of that infrastructure. For a business builder, the question is which of your assets are infrastructure — necessary but not differentiating — and which are genuinely proprietary. Infrastructure that is shared with partners or competitors can often be improved more quickly than infrastructure maintained alone.
A door still open.
A hypothesis worth testing: if a small business identified one internal tool or process it had built that might be useful to other, non-competing businesses, and shared it publicly, would it generate goodwill, partnerships, or candidate applications that exceeded the cost of sharing?
Which internal assets does your business maintain privately that, if shared, would create more value through collaboration than by exclusion?
Follow the evidence.
History is sourced below. Business lessons are editorial interpretations; future possibilities are questions to test, not predictions.
Prepared from primary-source histories. First edition: 25 Sept 2026.