On Fri, Sep 23, 2011 at 12:18 AM, David Weintraub <qazw...@gmail.com> wrote:
>
> Having a publicly available Subversion repository is the best way. The
> problem is what do you do if you don't have that.
VPN's are the usual approach to having access over the internet to
something that isn't public. OpenVPN is fairly simple to set up and
cross-platform.
> For multi-user projects, I've used Git. I keep the main Git repository
> is accessible via Dropbox, and everyone is suppose to be able to pull
> from it, but they're not suppose to push changes directly to the
> Dropbox repository. Instead, they're suppose to email me the patches,
> and I'll push them back to the Dropbox repository.
>
> I'm not a big fan of Git. Tracking patches and diffs is not the same
> as version control, and Git is just not as user friendly or as
> polished.
That's not the way you are supposed to use git. If your dropbox
location had sufficient space, consider how it would work if each user
had his own git clone there so you could pull what you want to merge
from them.
> I am still not convinced that Git is good in corporate environments.
> In those places, you want a centralized repository and the control it
> gives you.
Agreed, but you have to give the users access to the server either
with network connections behind your firewall or VPN access.
--
Les Mikesell
lesmikes...@gmail.com
