Hacker News Reader

Comment by ericfrederich | Hacker News Reader

I agree... I wish GitLab would do this too. No reason that everything can't be modeled as a git branch.

GitLab I know models their Wiki as a git repo. I think issues and PRs should be their own repo as well.... a branch for each issue or pr? Could tie it all up using submodules (or not, whatever)... just please someone take the jump first and do this.

View on HN

DISCLAIMER: I work for GitLab. We have a feature to replicate GitLab to different locations (EEP). We call it "Geo", which stands for "Geographical Replication". Part of the "Geo" effort is Disaster Recovery which is under heavily development. We want with Disaster Recovery to be able to reliably promote any Secondary node to a Primary, so if your US datacenter melts down under a nuclear war, you can start working with your copy in EU, India, China, etc.

If your US datacenter melts down under a nuclear war, I can guarantee that none of your devs will give a damn about contributing to the code base.

You might want to modify your scenarios.

As someone interested in these scenarios, where could I find out more information about what would happen post-nuclear explosion?

A lot of this is out in the open

There are active simulations going on: http://www.sciencerecorder.com/article.php?n=scientists-cond...

There are preparedness drills: http://www.independent.co.uk/news/world/americas/us-politics...

There's plenty of policy analysis: https://www.cato.org/publications/policy-analysis/social-eco...

Older .mil reports: http://www.dtic.mil/cgi-bin/GetTRDoc?AD=ADA080907

There are entire books taking apart what happens in specific fields: https://www.ncbi.nlm.nih.gov/books/NBK219154/

Or you could just read disaster porn^W^W post-apocalyptic sci fi.

So, a lot depends on what kinds of info you want to find. But overall, I'd say it's not worth reading, because life's not going to be much fun. Even if you're prepared.

it depends on your SLA ;)

In that event, how much would your "guarantee" be worth? b^)

(only partially serious here) I'm not sure recovery from a nuclear event that wipes out US data centers is economically feasible. If an event were to effectively wipe out 20% of the worlds economy I think having my github issues online is the least of my worries.

Yeah I know I'll be on vacation for a long while!

Hope it will be on the moon or in a nuclear shelter. Otherwise all that fallout may ruin your trip.

Reminds me of https://en.wikipedia.org/wiki/On_the_Beach_(novel)

If it's not Git based then I'm not interested in it.

I see no reason to have a RDBMS for issues, merge requests, pull requests, etc. All of these could be modeled in multiple ways using a Git database. Issues are files in a repo called issue1.md, issue2.md ... or issues are branches on a repo ... or something else.

Reply on news.ycombinator.com