Re: [git] Nebula plans of moving to git

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

> Wim Jongman <wim.jongman@xxxxxxxxx> 
> I wanted to ask this list for best practices.
I have been reading 
> that the best practice is to use different git repositories to 
> combine related projects or even use a single repository for each
plugin.

My experience has been that minimizing the number
of repositories is best. Each repository you need to work with adds the
overhead of doing push/pull/fetches, configuring properties, creating branches
and tags, etc. This affects committers, consumers, and adopters. For example
if I want to grab a couple of widgets from Nebula, creating and managing
two clones to do that is a pain. Also if you ever need to commit a change
that spans multiple repositories, you have lost ability to track that change
as a single commit, making it difficult to revert, cherry pick, etc. I
don't know Nebula very well, but I would suggest starting with a single
Git repository for all of Nebula, and only break it up if absolutely necessary.
Another project similar to yours would be Linux Tools, which is compromised
of several mostly autonomous components. They have used a single Git repository
for the whole project and it seems to be working well. I would only considering
breaking up a repository if it becomes physically too large to manage,
or requires different committer permissions for different parts of the
project.

John