3 ms·
Dang. It's too bad their customers' source control files aren't distributed and decentralized, or they could keep working and ignore this.
by peterwwillis 9y ago
Dang. It's too bad their customers' source control files aren't distributed and decentralized, or they could keep working and ignore this.
- toyg 9y agoThe problem is not the files, it's the project management stuff (issues and PR tracking). That is a SPOF. If they could decentralize that, then nobody would care if they are down half the time.
- mschuster91 9y agoI wonder why you can't export them as a read-only git repository. (Read-only to avoid people messing around with the history)
- csense 9y agoBecause that would make it easier to migrate away from Github, which Github doesn't want you to do.
- daxelrod 9y agoYou can actually export them, but the format is undocumented, and is meant only for import into GitHub Enterprise: https://developer.github.com/v3/migration/migrations/ https://developer.github.com/v3/migration/migrations/
- peterwwillis 9y agoThey can - it's called Github Enterprise (or if you're a medium to large corporation, JIRA). I thought occasional downtime was just something people factored into free services. You can always file your issues later, or use a chat service (or, heaven forbid, email) if there's an immediate need for feedback.