Hi everybody,
I intend to apply for this year's GSoC to work on libgit2 [1], namely "Finishing network support for libgit2" as outlined under [2].
>From my point of view, the idea makes a good GSoC project as
is, but more experienced developers might see potential pitfalls, for example regarding "pack-objects as a prerequisite".? (I haven't read / touched pack-related code before.)
So far, there's two things I would like to discuss in advance:
* What do you consider "the best" ssh library to be used? libssh [3] seems to be the way to go, though I've never used it before nor did I do any ssh related development. What about libssh2 [4]? (Site note: libgit2 aims to be as platform independent as possible.)
* In your opinion, what features make "a sane API for managing the user's SSH keys"?
(In case you want to discuss anything else / share ideas, please do.)
About me: I study Computer Science at FU Berlin [5], besides I do a Git-related part time job for a SCM company. As a regular contributor to libgit2 [6], I'm rather familiar with the community and the bigger part of the code base. GSoC would allow me to both gain experience with "Git's network stack" and to add an important yet missing core part to libgit2.
Thank you.
Michael (m1sc in #git, #git-devel, #libgit2)
[1] http://libgit2.github.com [2] https://github.com/peff/git/wiki/SoC-2012-Ideas [3] http://www.libssh.org [4] http://www.libssh2.org [5] http://inf.fu-berlin.de/en/index.html [6] `git log --oneline --author="schu-github"`