/home/michael

Distributed version control

2 min read

Note

Every contributor holds the full history, not just the current files.

In a distributed system, there is no single authoritative server that everyone depends on. Each copy of a repository is complete and independent. Work can happen offline, contributions can be merged from multiple sources, and losing one copy does not mean losing the project.

Distributed version control

One-sentence definition: Distributed version control is a system for tracking changes to files in which every contributor’s copy contains the complete history of the project, rather than connecting to a central store of that history.

The alternative is centralised version control, where a single server holds the history and contributors check files in and out. If that server fails, work stops. In a distributed system, every clone is a full backup — contributors can work independently and synchronise later.

Why distribution matters:

  • Resilience: no single point of failure. Any copy can restore the project.
  • Offline work: the full history is local, so you can commit, branch, and browse history without a network connection.
  • Parallel development: contributors work independently in their own copies and merge when ready, rather than serialising access to shared files.
  • Transparency: the complete history travels with the project. Anyone with a copy can see how it evolved.

Distinction from file syncing

Cloud storage (Dropbox, Google Drive) syncs current file states but does not record a meaningful history of changes. You can recover a recent version, but you cannot see what changed between versions, who changed it, or why. Version control tracks intentional checkpoints with descriptions, not automatic saves.

Relevance to open scholarship

Distributed version control makes the development of a scholarly project legible. Essays, datasets, and teaching materials can have auditable histories — showing how arguments evolved, where sources were added, and how collaborators contributed. Platforms like GitHub surface this history publicly, supporting the open scholarship principle that process, not just output, carries scholarly value. Git is the dominant implementation.

Sources

Notes

Git is by far the most widely used distributed version control system. Mercurial was a notable alternative but has largely ceded ground to git.

Continue reading

  • Git

    Git is a distributed version control system that tracks changes to files over time. It records who changed what and when, allows you to move between earlier and later states of a project, and lets multiple people work on the same files without overwriting each other's contributions.

  • YAML

    YAML is a human-readable format for storing structured data as plain text. In knowledge management and publishing workflows, it appears most commonly as the frontmatter block at the top of markdown files, where it holds metadata — title, author, date, tags — that tools can read without parsing the document itself.

  • Transform documents with AI

    Language models can transform documents into interactive tools in minutes. This post walks through a concrete example, turning a 21-page Word questionnaire into a working web app, and reflects on what that capability makes possible.

Graph View

Backlinks