From: Michael Schubert <schu@schu.io>
To: git <git@vger.kernel.org>
Cc: libgit2@librelist.org
Subject: [GSoC] Finishing network support for libgit2
Date: Thu, 22 Mar 2012 01:09:21 +0100 [thread overview]
Message-ID: <4F6A6DB1.1080202@schu.io> (raw)
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"`
reply other threads:[~2012-03-22 0:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F6A6DB1.1080202@schu.io \
--to=schu@schu.io \
--cc=git@vger.kernel.org \
--cc=libgit2@librelist.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).