** Andrew: Shawn Pearce going to be at Eclipsecon - Egit much needed for Linux communities; perhaps not developing features as rapidly as some would like because of Jgit vs. just relying on command-line tool (but this is required for multi-OS support)

+

** Bernd: Main developers just doing it in their sparetime - SAP thinking about actively contributing to Egit

+

** Boris: Apache going to support git (but not as their main repo), because somebody stepped up hosting certain projects in git format. Boris likes "git bisect"

Andrew: Shawn Pearce going to be at Eclipsecon - Egit much needed for Linux communities; perhaps not developing features as rapidly as some would like because of Jgit vs. just relying on command-line tool (but this is required for multi-OS support)

Bernd: Main developers just doing it in their sparetime - SAP thinking about actively contributing to Egit

Boris: Apache going to support git (but not as their main repo), because somebody stepped up hosting certain projects in git format. Boris likes "git bisect"

In Eclipse, checkout using commandline (not with Eclipse integration yet)

git at Eclipse: Most wanted Community addition by a factor of 5!

Biggest blocker is IP clearance missing for git (no time on IP Legal team to even look at it!)

2 Problems: (a) distributed nature leads to problems if genie is set loose

(b) Overhead of managing multiple repositories ... but that's only second order problem

We need a Doc package collecting information and arguments, but who could create it?

Martin thinks the biggest problem is that people discuss it who haven't really looked at it...

In favor of collecting experience and technical knowledge by hybrid approach first (CVS master + git children remote)

Martin is unsure about pros and cons of hybrid approach (cvs+git) vs git native at Eclipse.org

How to move forward: Use Public channels to collect facts, procedures, best practices - see Git for Committers