Open-source software - History Evolution and Summary

History of the Open-Source Movement Introduction The open-source movement represents a fundamental shift in how software is created, distributed, and maintained. Rather than being developed behind closed doors by a single company, open-source software is developed collaboratively, with its source code freely available for anyone to inspect, modify, and redistribute. Understanding how this movement emerged requires examining three key developments: the founding of the free software movement, the creation of Linux, and the strategic rebranding of the movement to gain broader business support. The Free Software Movement The open-source movement's intellectual roots trace to Richard Stallman, a legendary programmer who founded the Free Software Foundation (FSF) in 1985. Stallman was motivated by a specific frustration: he wanted to modify a printer's software but couldn't access the source code. This experience led him to develop a philosophy that users should have the freedom to understand, modify, and share the software they use. In 1989, Stallman created the GNU General Public License (GPL), a legal framework that guaranteed software freedom. The GPL was revolutionary because it used copyright law—typically a tool to restrict copying—to ensure the opposite: that software remained free and open. Any software licensed under the GPL must remain free, and any modifications must also be shared under the same license. The FSF also launched the GNU Project (which stood for "GNU's Not Unix"), a massive effort to create free versions of Unix tools and utilities. This was ambitious—they were essentially building an entire operating system from scratch, piece by piece. The Creation of Linux The missing piece in the GNU Project was a working kernel—the core component that manages a computer's hardware and resources. That changed in 1991 when Linus Torvalds, a Finnish computer science student, released the Linux kernel. What made this moment significant was the combination: GNU provided all the software tools and utilities, while Linux provided the kernel. Together, they formed a complete, functional, free operating system now known simply as "Linux." This wasn't just another piece of software—it was a proof that free and open-source development could produce a professional-grade operating system capable of competing with commercial alternatives. Linux's success demonstrated that collaborative, distributed development could work at scale and produce robust, reliable software. This practical success would prove crucial in convincing businesses that open-source wasn't just idealistic philosophy—it was a viable development model. The Emergence of the "Open Source" Term By the mid-1990s, the free software movement had created impressive software, but there was a communication problem. The word "free" in "free software" created confusion: did it mean free as in cost, or free as in freedom? More importantly, for many businesses, the ideological emphasis on user freedom seemed off-putting or even threatening. In 1998, Christine Peterson proposed a new term: "open source." This reframing kept the technical meaning—the source code is open and available—but removed the philosophical baggage. The term appealed to business logic: open source works because more eyes catch more bugs, because it enables rapid innovation, and because it reduces costs. That same year, the Open Source Initiative (OSI) was founded to promote this new framing and establish criteria for what qualifies as open-source software. The OSI didn't reject the free software philosophy; rather, they emphasized the practical, business-friendly benefits. This strategic rebranding proved remarkably effective. Companies that had dismissed "free software" as radical or impractical became willing to engage with "open source" as a legitimate development model. Free Software vs. Open-Source Software It's crucial to understand that "free software" and "open-source software" are not identical, despite significant overlap. Free Software (as defined by the FSF) is rooted in a specific philosophy about user freedom. The FSF identifies "four essential freedoms" that define free software: The freedom to run the software for any purpose The freedom to study how the software works and modify it The freedom to redistribute copies The freedom to improve the software and release improvements publicly These freedoms are about rights and ethics. A piece of software is either free software or it isn't, based on whether it guarantees these four freedoms. Open-Source Software has a broader and more flexible definition. It simply means the source code is available and can be examined. The OSI's criteria emphasize the practical benefits: code review, rapid development, innovation, and reliability. Open-source licenses often allow proprietary extensions or don't require all modifications to be shared publicly—as long as the original source is available. The Relationship Between Them Here's the key distinction: Almost all free software qualifies as open source, but not all open-source software meets the FSF's strict criteria for free software. For example, consider two licenses: The GPL (GNU Public License) is both free software and open source. It guarantees all four freedoms and requires all modifications to remain free. The Apache License 2.0 is open source but may not fully satisfy FSF's freedom criteria, as it allows proprietary derivatives without requiring them to share modifications publicly. This distinction matters because it reflects different priorities. Free software advocates prioritize user freedom as a moral imperative. Open-source advocates prioritize practical development benefits. Both support collaborative code development and transparency, but they diverge on questions like: "Must derivative works remain open?" <extrainfo> Adoption by Major Companies The shift from ideological opposition to mainstream acceptance accelerated over the 2000s and 2010s. Companies such as Microsoft, IBM, and Oracle—organizations that had once viewed open source with skepticism—now maintain major open-source programs and contribute developers to open-source projects. This corporate participation marked a fundamental validation of the open-source model and demonstrated its commercial viability. </extrainfo>