GitHub makes collaboration around code more visible

Context and provenance

GitHub's tenth-anniversary post identifies April 10, 2008 as its public launch and describes the initial aim of connecting developers around projects using Git. Looking back, it emphasizes not just repositories but teaching, documentation, contributions, and work built upon other work. This broader account is useful for reading software as a social artifact. The final program is only one outcome of decisions, discussion, review, and revision. A shared development platform can preserve some of those activities alongside the code itself. Its history also encourages a distinction between Git, the version-control system, and GitHub, a service built around collaboration using it; the two did not begin as the same project.

Why it matters

GitHub makes aspects of software collaboration available for inspection. Code history, documentation, and contributions can reveal how a tool was made, beyond the interface that users eventually encounter.

Sources and evidence

1. Thank you for 10 years