Sebastian Spier stellt das Thema vor

Repo-Rot is Real!

I help to maintain a GitHub org of 350 engineers on 3100 repos. What can we do to maintain some sanity with this amount of people, teams, and repos?

The longer a team exists, the more software components and repos they tend to have. How do you know, which of those are actively maintained, and which ones are not (they are rotting)?

This talk explores what I call "repo rot", which effect it might have on your team/company, and what you can do about it. I will show an experiment that I ran with my teams, and what we learned from it.