My team was working on merging pull requests when this happened.

We might actually be at fault! That would be kinda cool.

If only you were using a decentralized VCS, you wouldn't have this single point of failure…

The problem isn't the VCS part so much as all the code review/project management features of Github.

I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.

Yep, that was the one.

There's also plenty of DIY distributed issue tracker tools to keep issue tracking inside a git repo (often as yaml+markdown). I'm still surprised a good one hasn't stepped up with direct GitHub issue/project tool integration+sync, but that should certainly be a possibility.

Fossil SCM

the linux kernel development works just fine w/o github.

They use self-hosted git repo and bugzilla.

It's not exactly less of a point of failure.

I think the spf there is Linus' email account, right?

The VCS is decentralized but they made the process centralized.

but github is honestly so nice. I'll admit in a very subjective way. whats your favorite decentralized vcs?

The joke is that git is decentralized–it's just GitHub that's a single point of failure.

We have Gitlab Enterprise and it has trouble scaling.

Sorry to hear you're having trouble scaling GitLab. We have many organizations running GitLab and successfully scaling to 10's of thousands of users, and GitLab.com which is the largest GitLab installation. As a GitLab Enterprise customer our support team is happy to help you review your scaling problems and resolve them. Please submit a support request at https://support.gitlab.com.

O crap I meant to say GitHUB Enterprise. That's what has trouble. We also have Gitlab Enterprise and that's fine. Sadly for reasons internal we are mostly stuck with GitHub E.

I'm sorry to hear that. GitLab Enterprise Edition should scale fine to 100,000's of users. Are you in touch with our support about this?

thats why i asked what his favorite was. just curious to see what the feature differences would be

But reviewing, issues, PRs, etc. are. A lot of the planning parts are down.

> implying developers spend most of their time in editors.

Well the parent was implying they spend most of their time in Github.

I don't see that implication. I personally spend most of my time on GitHub.

I wouldn't be surprised if this became an issue in the future, with Atom's popularity on the rise…