A software company evicted the Linux community in 2005, and its replacement powers projects around the world

Published Oct 10, 2026, 9:00 AM EDT Simon is a Computer Science BSc graduate who has been writing about technology since 2014, and using Windows machines since 3.1. After working for an indie game studio and acting as the family's go-to technician for all computer issues, he found his passion for writing and decided to use his skill set to write about all things tech. Since beginning his writing career, he has written for many different publications such as WorldStart, Listverse, and MakeTechEasier. However, after finding his home at MakeUseOf in February 2019, he would eventually move on to its sister site, XDA, to bring the latest and greatest in Windows, Linux, and DIY electronics. The story of some of the biggest changes in open source began with a single, simple event. For example, Linux began as Linus Torvalds' pet project, and he never expected it to leave his bedroom. Valve's efforts with Proton to make Linux the gaming powerhouse it is today began with its desire to ditch Windows 8. But did you know that a single ban in 2005 shaped how developers around the world organise their coding projects? Well, if you've ever used Git in any shape or form, you have one disgruntled CEO to thank, even if he'd likely rather you didn't. . The early development of Linux was a bit of a mess People passed around code via email Back around the turn of the millennium, getting people synced up with their code wasn't too easy. In 2002, Linus Torvalds' solution was to use email. People would write patches or source code on their PC, attach it to an email, and then ship it off to everyone else. Sometimes they would bundle everything into a TAR file before shipping it off, something that would gain the moniker "tarball." But as more people joined and more code got written, Torvalds couldn't keep up with everyone shooting emails to one another. He needed a solution, and he settled on a Distributed Version Control System tool called BitKeeper. It wasn't open-source—it was owned by a company called BitMover, which was run by its CEO, Larry McVoy. However, McVoy had made Torvalds a pretty nice offer: he would allow the project to use BitKeeper's services for free, but at no point must any of the Linux developers attempt to reverse-engineer how BitKeeper worked. And if you've talked to an open-source developer for any longer than ten minutes, you probably already know how this deal ended. A Linux developer breaks the deal's terms and gets the community evicted Curiosity kills the cat... The Linux community thrived on BitKeeper for around three years, during which the operating system began to take form thanks to international efforts. However, the software could have been a bit better, but the Linux developers tolerated it for the most part. However, one developer, called Andrew Tridgell, didn't really want to shut up and make do. He figured that if he just took a peek inside the BitKeeper code to see what its network protocols were like, he could make a tool called SourcePuller that could better pull data from a BitKeeper repository without the proprietary software. An open-source developer's solution to a problem is usually to make their own tool, after all. Unfortunately, McVoy caught wind of this tool and declared that the Linux community had violated the one term of the deal. On April 5th, he revoked the Linux community's free licence with BitKeeper, essentially turning them out onto the digital street. Torvalds needed an alternative, and fast; however, unlike the situation he found himself back in 2002, he now had experience in how a Distributed Version Control System worked. So, proving once again how open-source developers solve problems, he decided to make his own. Linus Torvalds invents Git after 11 days of coding ...but satisfaction brought it back Credit: Github Come April 7th, two days after McVoy announced the eviction of the Linux community from BitKeeper, Torvalds was already hard at work making his own alternative. 11 days later, the tool is mature enough to manage its own source code. It's not quite ready to handle Linux just yet, but it was a start, and best of all, it was his own, open-source take on a vital part of kernel development. But all good projects need a name, and there were a ton of professional-sounding names he could have picked. However, he went with "Git," and he reveals a little as to why he picked this name in an interview with PC World: When asked why he called the new software, "git," British slang meaning "a rotten person," he said. "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git." The README for Git's source code plays with the name a little more: "git" can mean anything, depending on your mood. Random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant. Stupid. Contemptible and despicable. Simple. Take your pick from the dictionary of slang. "Global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room. "Goddamn idiotic truckload of sh*t": when it breaks. In June 2005, Git officially became the new home for the Linux kernel, starting with version 2.6.12. Three years after that, Chris Wanstrath, Tom Preston-Werner, PJ Hyett, and Scott Chacon recognised Torvalds' excellent work, but didn't like how difficult it was for people to find other Git projects to work on and download. They would go on to develop and release GitHub, a central place where people could post, share, and download repositories. And the rest, from there, is history. One ban was all it took to spark Git's creation Who knows how the world of development may have looked if McVoy never banned the Linux community from BitKeeper? Perhaps we'd still be using it today. Regardless, the CEO's move helped create the second-biggest open-source project Torvalds invented.