Do yourself a favor and get a real git repository. Using dropbox is indeed super easy but has two major caveats:<p>1. Git is agnostic to updates to the repo, as dropbox is not a supported transport method (as opposed to SSH for example). So, for example, git hooks won't work.<p>2. Dropbox is extremely susceptible to repo corruption in case of simultaneous updates. Restoring a corrupt repo is not a pleasant task.<p>For your sanity - don't do it.
At this time and age, I think designers should learn how use git. It's a tool like anything else.<p>Specially if your only concern is updating the images, the process should be pretty straightforward, you don't need to learn anything advanced.
Given how often I get synchronization conflicts on regular files with Dropbox, I would be quite wary to use it to put and synchronize repositories there. The problem is (obviously) that Dropbox is really a local synchronized folder, so a Git push will only be reflected on Dropbox if there is an opportunity to sync. So, if you have mobile coworkers, it's easy to mess up things.<p>Given that there are many companies who offer repository hosting for just a few dollars per month (also for teams), I cannot see why one would go this route.
What are the real advantages of using version control from the designer point-of-view?<p>In most cases, a good backup system is what they need. Use Apple's Time Machine or Crashplan and backup every 15 minutes automatically.<p>From a programmers point of view VC is great. We actually have the tools to deal with different versions of text files: find differences, resolve conflicts, merge, split off new versions, etc.<p>And designers? What do they get beyond a more complex and opaque form of Backup. Sure it makes it easier to get the designers output into our programmers workflow, but the way this is usually sold is a Pain in the designers backside with no real benefit.<p>If programmers want to win over designers to version control, we need to sell them on real advantages. We need to show them tools like pixelnovel's timeline that integrates SVN diretly into Adobe CS and provides an in app version viewer. Or Kaleidoscope.app which allows the visual comparison of image (and text!) files.<p><pre><code> http://pixelnovel.com/ (SVN only)
http://www.kaleidoscopeapp.com/ (Git, Mercurial, SVN & Bazaar)
</code></pre>
However, even these tools only scratch the surface of the power that programmers gain from the pain of version control.
Hylke Bons wrote a very nice git-based Dropbox alternative with focus on collaboration called SparkleShare (<a href="http://www.sparkleshare.org" rel="nofollow">http://www.sparkleshare.org</a>). It's still in beta state but a few members of the GNOME design team are already using it to collaborate.
What's the difference between this and just using github? I think it's just the daemon-ness of dropbox. It would be cool to have something similar for arbitrary git repos that runs 'git fetch' periodically in the background. (or something fancier, if you want to scale it out) That keeps the conflict management at the git level, and you aren't keeping history of history anymore.
I regularly work across multiple computers(all macs, but 2 desktops and my laptop), so I actually put my virtualenvs in my Dropbox and then they contain git repositories. So I have my full environment installed on all the computers all the time.<p>You do have to install git, virtualenv and pip on all the computers, but thats not too much to ask.
The open source SparkleShare gives users the same feel of Dropbox, while using Git as its backing storage:<p><a href="http://www.sparkleshare.org/" rel="nofollow">http://www.sparkleshare.org/</a><p>It currently has native clients for Linux and Mac, with Windows coming soon.