Lesson 1 of 6 · 10 min
What is Git and why open source runs on it
Version control in plain language, and how thousands of volunteers build software together.
The problem Git solves
Imagine you and three friends are writing a project report together, each on your own laptop. You email files back and forth: report-final.docx, report-final-2.docx, report-FINAL-really.docx. Someone overwrites someone else's work. Nobody remembers which version was correct.
Git fixes exactly this for code. It is a version control system: it records every change you make, lets you go back to any earlier state, and lets many people work at the same time without overwriting each other.
Why open source depends on it
Every major open source project — Linux, Python, VS Code, the software FOSS Andhra builds — lives in a Git repository ("repo"). A repo is the project's folder plus its entire history. When you hear "clone the repo", it means: download the project and all of its history, so you have everything locally.
This is why open source works at massive scale with volunteers who have never met: Git records who changed what, when, and why (in the commit message). Trust comes from the history, not from knowing each other personally.
The vocabulary you need today
| Term | Plain meaning |
|---|---|
| Repository (repo) | A project folder tracked by Git |
| Commit | A saved snapshot of your changes, with a message |
| Branch | A parallel line of work, like a rough draft |
| GitHub | A website that hosts Git repos so people can collaborate |
Note: Git and GitHub are different things. Git is the tool on your computer; GitHub is where repos are shared — like the difference between a word processor and Google Docs.
What's next
In the next lesson you will install Git and set up your identity, so every commit you make is credited to you.