Hi, just a first answer about the Git plugin, about each of your points
- This is the normal workflow, the only one supported by the Git plugin (whom I authored). Will work flawlessly up to a certain point where your history will slow down any new git clone. In a local network and with a small team this might not be a problem. But IT IS for projects with many peoples needing to synchronize across Internet (and with many new people wanting to clone the whole repository often).
- git-fat, git-media and git-annex could (should?) work with the git plugin (as the new github LFS), but I never tried
any of them as 1) always served my needs. Would love a feedback though! - submodules are not supported by the git plugin for now, but is would be a good improvement to think about in the future.
- subversion is not supported by the git plugin
- subversion is not supported by the git plugin
- no source control is not supported by the git plugin
Also, you should certainly differentiate Blueprints to all other assets, as only Blueprints are Visually Diff-able.