Personally: svn and Mercurial Intel uses git. However, we have had significant trouble keeping git repos alive and clean in projects involving many developers that are geographically dispersed. As a result, we've had to dedicate resources - full-time people whose sole job is to maintain the git repos as it requires someone with very high git knowledge to continually fix the problems. This doesn't require one person/project, but it does require (a) significant time, and (b) deep git knowledge.
The basic issue I'm hearing is the same we have surfaced before: git exposes a lot of atomistic controls. This makes it very powerful, but also very easy to make an error as it requires a high level of git-knowledge to properly operate the system. Many developers lack that degree of "git IQ", and don't take the time to learn it as they are under pressure to produce actual code, or think they have it but don't know as much as they think. As a result, the repo (main or the developer's branches) get confused and need to be corrected. Bottom line: so long as OMPI has at least one git-expert on the team who can dedicate some of their time to helping developers "fix" their repo problems, the proposed transition could be done. I'm not talking about someone who will monitor/repair the main repo - I'm talking about someone also willing to assist every member of the devel team when that person's git branch gets hosed. If we ever lose that dedicated support, we may be in trouble. Unlike a corporation, we can't hire someone to fill this role. We rely on contributed time from our members. So I think the question boils down to: do we have that kind of commitment from our member organizations for the foreseeable future? And should we adopt a technology that depends on that contribution? Ralph On Wed, Apr 16, 2014 at 3:34 AM, Mike Dubman <mi...@dev.mellanox.co.il>wrote: > git > > > On Wed, Apr 16, 2014 at 1:32 PM, Jeff Squyres (jsquyres) < > jsquy...@cisco.com> wrote: > >> What source code repository technology(ies) do you use for Open MPI >> development? (indicate all that apply) >> >> - SVN >> - Mercurial >> - Git >> >> I ask this question because there's serious discussions afoot to switch >> OMPI's main SVN repo to Git, and I want to get a feel for the current >> landscape out there. >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> For corporate legal information go to: >> http://www.cisco.com/web/about/doing_business/legal/cri/ >> >> _______________________________________________ >> devel mailing list >> de...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2014/04/14537.php >> > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/04/14538.php >
