The Evolution of Open Source Software: From GNU to Modern Libraries

Every time you search a library catalogue online, place a hold on a book, or browse a digital repository of old theses, there is a good chance the system running behind the scenes is open source software. But this technology did not appear overnight. It grew out of a decades-long movement that began with one programmer’s frustration, gained momentum through a student’s hobby project, and finally earned the name we use today through a single brainstorming session in California. Understanding this development path helps explain why open source tools have become so important for libraries, especially those working with limited budgets.

Early conflicts and the Free Software Foundation 🔗

The story begins in the early 1980s with Richard Stallman, a programmer at the Massachusetts Institute of Technology (MIT). At the time, software was increasingly being locked away. Companies began selling programs without sharing the underlying source code, and they required developers to sign nondisclosure agreements. For Stallman, who came from a culture of programmers freely sharing and modifying each other’s code, this shift was deeply troubling.

On September 27, 1983, Stallman posted an announcement declaring his plan to build a complete operating system that anyone could use, study, modify, and share. He called it GNU, a recursive acronym meaning “GNU’s Not Unix.” The goal was to create a free replacement for the popular but proprietary UNIX operating system. As Britannica notes, the name was a playful jab at UNIX while making clear the project was something entirely independent.

The word “free” here is the source of much confusion. Stallman never meant free as in zero cost. He meant free as in freedom. The idea was that users should have the liberty to run a program, examine how it works, change it, and pass it on to others.

Building an institution around the idea 🔗

An idea needs structure to survive. In 1985, Stallman founded the Free Software Foundation (FSF), a nonprofit organization whose initial purpose was to support the GNU Project. According to the FSF’s own history, this marked the organizational home for the project and gave it the infrastructure to keep going.

One of Stallman’s most lasting contributions was the concept of copyleft, a clever legal mechanism that uses copyright law to guarantee freedom rather than restrict it. He put this into practice through the GNU General Public License (GPL), first released in 1989. The GPL requires that anyone who distributes the software must also pass on the same freedoms to others. This single licence would later become the legal backbone for some of the most important software in the world.

The rise of Linux and Linus Torvalds’ contribution 🔗

By the early 1990s, the GNU Project had produced a remarkable collection of tools: a compiler, a text editor, a debugger, and many system utilities. But one critical piece was missing. The project still lacked a working kernel, the central core of an operating system that manages hardware and connects it to software. Without a kernel, all those excellent tools could not yet form a complete, functioning system.

The missing piece arrived from an unexpected source. In 1991, a 21-year-old Finnish student named Linus Torvalds at the University of Helsinki began working on his own operating system kernel as a personal hobby. On August 25, 1991, he posted a now-famous message to an online newsgroup describing his project, modestly saying it was just a hobby and “won’t be big and professional.” He could not have been more wrong about its future.

How a hobby became a revolution 🔗

Torvalds wanted to call his kernel “Freax,” a blend of “free,” “freak,” and “x.” But an administrator at the university’s file server renamed the folder to “Linux,” and the name stuck. The early versions were rough, but Torvalds kept releasing updates rapidly, and developers around the world began contributing.

The turning point came in 1992, when Torvalds released the Linux kernel under the GNU GPL. This decision was crucial. It meant the kernel could be combined with the GNU tools that Stallman’s project had already built. As the Internet Hall of Fame describes it, this combination filled the last gap, producing a complete and free operating system widely known today as GNU/Linux.

This collaboration proved something powerful: software built by thousands of unpaid volunteers, scattered across the globe, could match and even surpass commercial products built by paid teams. By 1993, more than a hundred developers were already working on the kernel. Today, Linux powers everything from smartphones and servers to the world’s most powerful supercomputers.

Formation of the Open Source Initiative 🔗

Despite these successes, the movement had a marketing problem. The term “free software” kept causing confusion. Newcomers and businesses assumed “free” meant no cost, and supporters constantly had to explain the difference between “free as in freedom” and “free as in beer.” This confusion was holding the movement back from wider adoption, particularly in the business world.

The breakthrough came in early 1998. The web browser company Netscape had just decided to release the source code of its browser, generating fresh excitement and discussion. A group of leading figures gathered for a strategy session to find a clearer term that would appeal to businesses without the philosophical baggage.

Christine Peterson and a better name 🔗

At that meeting was Christine Peterson, then the executive director of the Foresight Institute, a think tank focused on nanotechnology. She was not a software developer like most others present, but she recognised the core problem clearly. According to her own published account, the existing terminology turned discussions about software into confusing conversations about the price of a beverage.

Between meetings that week, Peterson came up with the phrase “open source software.” She felt it shifted the focus to what really mattered, the availability of the source code, rather than the politically loaded idea of freedom. As she later explained, the term was a deliberate effort to make the field more understandable to newcomers and to business. She quietly proposed it to colleague Todd Anderson, who raised it in the meeting, and the group gradually embraced it.

Soon after, in late February 1998, the Open Source Initiative (OSI) was founded to act as the steward of this new term, with Eric Raymond as its first president and Bruce Perens as vice president. As the OSI’s history records, one of its first tasks was drafting the Open Source Definition, a set of criteria that software must meet to be called open source. Notably, even Linus Torvalds quickly supported the new label, helping it spread rapidly through the community.

Open source in libraries today 🔗

All of this history matters because it created the foundation for tools that libraries now rely on every day. For libraries, especially those operating on tight budgets, open source software solves several practical problems at once. It lowers initial and ongoing costs, eliminates dependence on a single vendor, and gives libraries far greater control over their own data and systems.

Proprietary library systems can be expensive. The cost of a commercial system can exceed the entire annual budget of a mid-sized library, and the spending never truly ends because of recurring fees for updates and support. With open source, the software itself is free to download, use, and modify. This is a major reason why so many library automation projects across India have adopted open source tools.

Koha: the first open source library system 🔗

Koha is perhaps the best-known example. Launched in 2000, it was the first free and open source Integrated Library System (ILS). The name comes from a Māori word meaning “gift” or “donation,” which fits the spirit of the movement perfectly. Koha is web-based and handles all the core functions of a library, including cataloguing, circulation, patron management, and acquisitions, as detailed in this INFLIBNET module on the software.

Koha has been particularly successful here because of its ability to handle multiple Indian languages, and it has been installed in academic, public, and special libraries of all sizes. The Delhi Public Library is one well-documented case of a large traditional library moving to Koha for its automation needs.

DSpace and Greenstone for digital collections 🔗

Beyond managing physical books, libraries also need to preserve and share digital content such as theses, research papers, photographs, and rare manuscripts. Two open source tools dominate this space.

DSpace is repository software designed for the long-term storage, indexing, preservation, and distribution of digital scholarly content. Many universities use it to build institutional repositories that showcase the research produced by their faculty and students.

Greenstone is another widely used tool for building and distributing digital library collections. Produced by the New Zealand Digital Library Project at the University of Waikato, it is developed in cooperation with UNESCO and is released under the GNU GPL, the very same licence that grew out of Stallman’s work decades earlier. Greenstone has been especially popular in developing countries because it offers a low-cost way to organise and publish information, supports multiple languages, and lets institutions build their own collections without deep technical expertise.

Why this matters for the future 🔗

The advantages of open source for libraries go beyond saving money. Because the source code is open, libraries can customise the software to suit local needs, whether that means supporting a regional language or adding a specific feature. They are no longer locked into one company’s product or pricing. They also benefit from a global community of users and developers who continuously improve the tools and offer support.

There are trade-offs to consider. Open source software demands a greater degree of technical responsibility from library staff, who must handle installation, maintenance, and troubleshooting, either in-house or through service providers. But for many institutions, this responsibility is a fair exchange for the control and freedom they gain.

The journey from a frustrated programmer at MIT in 1983 to a thriving ecosystem of library tools shows how a principled idea about freedom and collaboration can reshape an entire field. The next time you use a digital catalogue or download a thesis from a university repository, you are benefiting from a development path that took nearly two decades to build.

What do you think? If your library had to choose between a polished commercial system with guaranteed support and a flexible open source system requiring more technical skill, which would serve your community better? And do you think the freedom to modify and control software is as important for libraries as the cost savings it offers?

References

1. https://www.gnu.org/gnu/initial-announcement.en.html
2. https://www.britannica.com/biography/Richard-Stallman
3. https://www.fsf.org/history/
4. https://www.stackscale.com/blog/linux/
5. https://www.internethalloffame.org/inductee/richard-stallman/
6. https://opensource.com/article/18/2/coining-term-open-source-software
7. https://sdtimes.com/os/history-behind-term-open-source/
8. https://opensource.org/about/history-of-the-open-source-initiative
9. https://digitalcommons.unl.edu/cgi/viewcontent.cgi?article=8349&context=libphilprac
10. https://ebooks.inflibnet.ac.in/lisp5/chapter/koha-open-source-integrated-library-software/
11. https://www.greenstone.org/