Repo backups

[edmundmiller]

From @ewels in slack

Ok, after thinking about this a bit more, I think I would like to totally ignore the fact that the vote just went 9:0 in one direction and do the other thing that no-one voted for 😆
😆

I think that the "back up everything" setup will be quite a lot more complicated to set up and more likely to break. I don't want to ever think about this again once it's done, I want it to be totally bombproof and reliable. The "back up everything" setup will likely be too complex to meet that criteria.

So my proposal is:

• Have a GitHub action that does a matrix over all repos, clones the repo, tarballs it and uploads it to s3
• Run weekly
• Have an s3 retention policy that deletes files in this bucket after 1 year

The other setup was more complicated and I worry I'd never get around to it / it'd break over time.

I suggest that we do manual "full backups" periodically if we want, in addition to the above. For example as part of spring cleaning or something.

Or we can add that in as an additional monthly backup in the future if we want, for example