[smtddr]

>>A little downtime from time to time can't be avoided. People just love to complain.

If you feel this way then image-editing isn't your core task in your job.

Imagine if the github.com maintainers had your attitude. "Meh, some downtime here 'n there. Whuchagonnado?" A github outage for _OVER 24 HOURS_ would freakin' wreck me and my coworkers. The image-editing department for a high-fashion magazine in New York or Paris with those already near-impossible deadlines losing 24hrs is going to make some execs somewhere very angry.

[sureshv]

I would think git's distributed nature would make this a lesser issue. You would just have to set up another remote target and push/pull from that (say on AWS or some other provider).

[e12e]

Sure. But not having access to the tickets database might cripple a team pretty badly.

One reason I'm still toying with the idea of trying fossil[1] "for real" and/or find/make a tool that distributes issues within mercurial/git like http://www.bugseverywhere.org/

Note-to-self: looks like hattawiki might be a nice companion on the path to "distributed everything":

http://hatta-wiki.org/Install

[1] https://www.fossil-scm.org/

[pedrocr]

For a distributed wiki try gollum. It's the wiki engine behind the github wikis and it's basically a wiki where the database is a git repo. I love it for family use. I can put up a nice web interface for everyone else to edit and yet I use git push/pull and my normal text editor. Works great.

[gohrt]

Turn it around into a special no-Photoshop issue of the magazine, and disrupt the high-fashion industry!

[voltagex_]

No one other than Adobe can provide a Creative Cloud that you can type cc add remote creativebucket.org and keep working. You can, however, type git add remote bitbucket and should be working to several remotes.

[l0stb0y]

And yet another fashion magazine expert. So many! I'd like to point out that your image is solely based on low-grade chick-flicks.