With your firewall issues you will probably be better served with the
distributed VCS tools, like Mercurial, Git, etc...  They give each
developer a full copy of the repository, so they won't need to be
accessing over the network all the time.  However, they are more
complex.


On Thu, May 6, 2010 at 10:42 AM, John  BORIS <jbo...@adphila.org> wrote:
> I understand the resistance to something new. One thing that is in the
> mix that I left out is that my network sits behind a firewall that I
> have no control over. So when I install this I have to work with our IT
> shop to poke the right holes in the Firewall for my remote programmers
> to access the repository. We use Juniper's VPN product for outside users
> to gain access. Maybe that is the reason my remote programmers didn't
> care for our other forays into this worked as the VPN process was a
> chore for them.
>
> This is a new venture. the previous ventures were failed attempts and I
> never did get the repositories built properly and since I am the one
> that has to manage things and setup the way it has to be used I guess I
> added to the frustration as I didn't know how to do certain things.
>
> Anyway I will look at the other products as well as looking back at
> SVN.
>
> Thanks for the quick reply.
>
> John J. Boris, Sr.
> JEN-A-SyS Administrator
> Archdiocese of Philadelphia
> "Remember! That light at the end of the tunnel
> Just might be the headlight of an oncoming train!"
>
>>>> Brian Mathis <brian.mat...@gmail.com> 5/6/2010 10:26 AM >>>
> Subversion is one of the more straightforward systems out there, so if
> the programmers don't like it, get new programmers ;)?  Any VCS is
> going to be an adjustment for programmers to use if they are not used
> to using it.  It's very difficult to have one that "just works"
> without the programmers taking some action to check in/out code, so it
> will definitely be something they need to get used to.
>
> Bottom line is that VCS something that's so important that your
> organization will need to force it upon them if there is resistance.
>
> There are many tools for systems like subversion that make it easier
> to use (if they were objecting to using the command line).  Take a
> look at tortoisesvn, which does a great job integrating svn into
> Windows, and there are often plugins for whatever development
> environment you are using.  Do some googling.
>
> Also, there are now many new VCS systems out there, such as Mercurial,
> Git, etc...  I *strongly* recommend that if you are starting new, take
> a look at them first.  They are slightly more complex, but also
> provide many more benefits than SVN.  There are also GUI frontends to
> them available.
>
>
>
>

_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to