3 ms·

Repo hosts are quite vulnerable to storage abuse as well as simply accruing genuine old content. I can see a deletion heuristic that considers both account act

Repo hosts are quite vulnerable to storage abuse as well as simply accruing genuine old content. I can see a deletion heuristic that considers both account activity and repo activity being deployed within the next 10 years. However I expect another evolution in SCM in the same timeframe.

rodw 7y ago
Right, look at SourceForge. There's a lot of broken links and/or references to no-longer accessible content in some of the older Apache.org projects too. Also maybe cvs/svn/git repo generally don't contain content worth preserving for 100 years. There are some historically significant or interesting repos, but for the most part you'll have a bunch of unremarkable (and duplicated) code that may not have run then and certainly won't run now.
- TeMPOraL 7y ago
  > a bunch of unremarkable (and duplicated) code that may not have run then and certainly won't run now 100 years is a long time, but I do run 20+ years old Common Lisp libraries and expect them to work without modification; I'd be really pissed if they disappeared from the Internet because someone thought that 5 years of inactivity means something doesn't work anymore.