Esmond Kane
Forge now has Git support so I've been busy revisiting the buzz around distributed version control. A nice graphical illustration of DVCS is here: http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/
Potentially Forge has hosted some element of DVCS for some time. SVN has a distributed fork SVK (http://svk.bestpractical.com/view/HomePage). Git also offers transparent SVN support (http://www.flavio.castelli.name/howto_use_git_with_svn).
As with any polarizing topic, the opposing SCM camps offer many viewpoints and there are lots of online comparisons of DVCS (Git/Cogito vs Bazaar vs Mercurial vs Darcs etc) vs CVCS (CVS vs SVN vs Perforce vs Arch etc). Theres a nice hg-biased perspective here: http://www.dribin.org/dave/blog/archives/2007/12/28/dvcs/. Please chime in with your perspective, we will escalate any concerns over the Forge implementation (or lack thereof) to the vendor.
Putting aside the political hubub, I stumbled across GitHub (http://github.com/). Its main feature is Campfire and Lighthouse integration for the whole 2.0 GTD crowd. Like Forge, it adds a happy medium to the DVCS vs CVS debate and integrates additional project management features (ticketing and task management, communication etc). Unlike Forge, it looks to be expensive to scale beyond simple public hosting. Discussions |
| Locked |
Sticky |
|
|
|
|
|
| There are no threads. |
|

The Harvard ABCD Forge is an installation of the GForge project and is supported and maintained by the ABCD Software Developers Group. Funding is provided by the office of the
Harvard CIO. Contact the forge-admin team with any
questions. Our privacy policy is posted
here.