Using libgit2 code in git.git as a Google Summer of Code project?

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Mar 10, 2011, 10:13 UTC
Message-ID: <20110310101332.GC26851@elie>
In-Reply-To: <AANLkTikkFDLKn5KMaSTwUABBVX_vYDj8pW1kqmsm1_vy@mail.gmail.com>

Hey Vicent et al,

Vicent Marti wrote:

Show 8 quoted lines

>                                                           there have
> been proposals to merge parts of libgit2 into the original Git client;
> however, this is not one of our priorities (we are designing git.git
> to be embeddable in Git backends and GUI programs), and the library is
> not yet stable enough for that kind of job. We'll see what the future
> brings -- git.git would certainly benefit from some of our code, if
> anything because it's (slightly) faster and cleaner than the original
> implementation.

I've been thinking that it would be interested to start this work early on, partially so that libgit2 and git.git can get to know each other better so to speak (which could help libgit2 along nicely and help git get past some old limitations, I think). So I'm thinking of proposing stealing some of your code, with an eye toward eventually making git "just another libgit2 user", as a Google summer of code project idea.

Is that a sane idea? Is there any particular subset of the lib that would be an interesting place to start? Do you forsee any obstacles? Do you know anyone who might be interested in mentoring such a project?

Admittedly I'm not so familiar with libgit2 yet, so I'm willing to believe the answers might be no, no, yes, and no. ;-)

The Google Summer of Code application deadline is this Friday (March 11) at 23:00 UTC. If this does seem like a sane thing to do, it might be nice to put it on the ideas page at:

  https://git.wiki.kernel.org/index.php/SoC2011Ideas

Thanks for your work. Jonathan