Shaun Mangelsdorf <s.mangelsd...@gmail.com>

Hi All,

It's come time again to revisit the idea of using git for development of the
ESOE project. A few things have changed since this was last discussed, not
the least of which is the transition to Redmine (http://www.redmine.org) for
managing the project.

With the revamped project site, we can now use (almost) any VCS we want. The
only feature missing is continuous integration which we can address later,
outside the scope of this discussion.

I'd be keen to hear any arguments against git, but in the absence of any
strong opposition I would say the move to git is inevitable. I believe that
tool support is now solid enough that we can make the transition smoothly.
There is one main question I put out to the esoe-dev list:

How should the Git repository be structured? I see two options really:

- One monolithic git repository with a mirror of the current structure of
the svn trunk

Advantages:
* Atomic branching and tagging, treating all the code as a unit.
* Only one history timeline to manage.
* Repository introspection will continue to function properly - Redmine can
only properly link one source repository with a project.

- One git repository per project (broken down per Eclipse project)

Advantages:
* More "correct"
* Easier for other projects to consume our code as submodules

I'm keen to hear of any more advantages to either approach, or any other
thoughts. My preference currently is for one repository, but it's certainly
not set in stone.

Regards,
Shaun Mangelsdorf