Re: [vhdl-200x] Code sharing options

On Tue, May 3, 2011 at 4:55 AM, Martin.J Thompson
<Martin.J.Thompson@trw.com> wrote:

> Further reading: http://en.wikipedia.org/wiki/Distributed_revision_control
>
> Other useful features which can come with code-sharing systems are:
> * Web based interfaces
> * Windows Explorer integration
> * Mac Finder integration
> * Code review (by email or online)
> * Automatic merging of branches

I would add *Education and *Community-building as features. I am
only familiar with github, but there I can follow changes by repos, by
developer etc. During my unemployment, I have been using github to
learn Scala and Lift. With github I can answer most of my own
questions by following the developers and the code I am learning
without bothering anyone.

> Personally, having worked on an (open source) project distributed across countries with a number of developers, distributed version control is brilliiant.  We also ran it in tandem with enforced code review by a rigorous core group which ensured that coding standards were followed.  This produced readable and clean code which wasn't obviously written by a whole gang of different people with different ideas of how to lay code out.  It makes it much more accessible - once you have more than one developer, I think this is crucial.

I agree.

> * Git - written to manage the linux kernel.  It's *very* fast, but works bit differently to other systems.  http://git-scm.com/

Note that git is a program, while github is a worldwide network of
code and people. If I pay for my github repo, I can make it as private
as I like.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.