Infrastructure for Git, built on social
On 10 April 2008 GitHub was publicly launched, a hosting platform for Git repositories founded in San Francisco by Tom Preston-Werner, Chris Wanstrath and PJ Hyett (with Scott Chacon joining a few months later as fourth co-founder). The site had been in beta since October 2007 and is built on Ruby on Rails — consistent with the era’s startup ecosystem.
Context: Git was released in April 2005 by Linus Torvalds as BitKeeper replacement for the Linux kernel. In the following three years it has gained following as distributed version control system (DVCS), but no hosting infrastructure yet exists designed around its characteristics. Generalist hosting (Sourceforge, Google Code, Gitorious) treats Git as one repo among many.
What changes with GitHub
GitHub introduces a collaboration model extending Git with social features native to the platform:
- One-click fork — anyone can duplicate a repository under their own account, without special permissions
- Pull requests — external contributions proposed as inline code-reviewable requests, with discussion threads per commit/file/line
- Integrated issue tracker with
#Ncommit references - Gist — snippet sharing with Git versioning
- User profile with contribution graph, following and followers, starred repositories
- Code browser with syntax highlighting for dozens of languages
- REST API for automation
The design does not just host Git: it makes it social. This is the most important conceptual contribution.
The business model
GitHub adopts a freemium model:
- Free public repositories — default mode, attractive for open source projects
- Paid private repositories — tiered plans (USD 5, 12, 22 monthly early on) for teams wanting isolation
The model is sustainable because public repositories — though free — generate value: they populate the catalogue, attract users, push Git adoption itself, build platform reputation. Paying customers sustain the infrastructure.
In 2008 this model is not obvious: Sourceforge relies on advertising, Google Code is free but doesn’t monetise. GitHub shows that “open source first, paid privates” is economically viable.
Effect on Git adoption
Before GitHub, Subversion dominates enterprise teams and Git is adopted in technical niches (Linux kernel, some Mozilla projects, Ruby outposts). GitHub dramatically lowers the usage barrier:
- The web interface makes many operations accessible without deep Git knowledge
- The fork + pull request pattern is easily understandable even by junior developers
- Integration with GitHub Pages (to come) and external CI facilitates modern workflows
Git adoption accelerates measurably from 2008-2009. Within a few years the GitHub model becomes the de facto standard for open source projects at any scale.
The social coding culture
The most lasting impact is arguably cultural. GitHub introduces practices modifying software development:
- Readable commits — encouraged by public profile visibility
- README.md documentation — Markdown by default in GitHub browser
- Pull requests as objects of discussion — the idea of “modification proposal” becomes collaboration currency
- Public profile as CV — recruiters start asking for GitHub profile alongside the resume
- Micro-scale open source — individual projects published for sharing, even without broad-adoption ambition
These practices spread beyond GitHub itself and influence competing tools and platforms (Bitbucket, later GitLab from 2011).
Emerging competitors
As of 2008-2010 the field is not yet consolidated:
- Bitbucket (2008, acquired by Atlassian 2010) — initially Mercurial focus, later Git
- Gitorious (2008, open source) — self-hostable alternative
- Google Code — generalist, declining after 2011
- Sourceforge — dominant in the previous decade, in difficult transition
- Launchpad (Canonical) — Bazaar focus, Ubuntu niche
GitHub’s advantage is user experience and network growth: each user attracts users, each project improves critical mass.
What happens next
In the following years GitHub grows to become the main open source code repository in the world, with tens of millions of developers in the early 2010s. Microsoft’s USD 7.5 billion acquisition in June 2018 will consolidate its role in the enterprise ecosystem, introducing native CI/CD features (GitHub Actions, 2018-2019) and Codespaces.
As of 2008 all this is still far away. But the foundational setup — social Git hosting with fork, pull request, public profile, freemium model — is fielded from birth and remains substantially unchanged for fifteen years.
In the Italian context
In 2008 Italian Git adoption is limited and tied to advanced development groups (academic research, tech startups, Ruby/Python development niches). Most Italian enterprise teams still use Subversion or proprietary systems (Perforce, ClearCase).
GitHub will measurably accelerate Italian Git adoption in the next three years; by 2011-2012 it will be the reference platform for open source projects published by Italian universities, hackerspaces, early PA projects.
References: GitHub Inc., founded April 2008. Tom Preston-Werner, Chris Wanstrath, PJ Hyett, Scott Chacon. Git (Linus Torvalds, April 2005). Ruby on Rails. Freemium model. Microsoft acquisition June 2018.