From: Vicent Marti <tanoku@gmail.com>
To: git@vger.kernel.org, srabbelier@gmail.com
Subject: Libgit2 on the Summer of Code
Date: Thu, 27 May 2010 18:25:32 +0200 [thread overview]
Message-ID: <AANLkTil-M3kQGbRZIacItlwr37Lf3lso7FspftLr43_F@mail.gmail.com> (raw)
Hello fine gentlemen,
I believe a short introduction is due. My name is Vicent Marti and I'm
the Google Summer of Code student who will be working on libgit2 this
year. If you haven't heard of it before, libgit2 [1] is a C library
which intents to re implement all of Git's core in a saner, reentrant
manner, with proper error handling and all the usual stuff you'd
expect from an actual library (including a less restrictive license).
I'm being kindly mentored by Scott Chacon on this task, and it seems I
might have been a *tad* too much mentored (;d), because I've spent so
much time discussing things with Scott and the other libgit2
developers that Sverre Rabbelier had to remind me that there's an
actual Git mailing list and I haven't even introduced myself to it
yet.
Well, fear do not. I'm here (a couple weeks late, but here after all)
and although I have been slacking on the community interaction part of
the Summer of Code, the actual project is well under tracks:
All the milestones for the first coding period are mostly finished
(yay for that) and you can find the code and follow my progress on my
public github repo [2]. There is some documentation in place, and
there are some tests in place. In the following days I'll aim for
about 90% code coverage on the tests, to finish the documentation, and
then prepare the patch series for review on this list.
Meanwhile, you are very much welcome to start flaming away before the
patch series are ready. We have roughly one month and a half to fix up
my code to the project's standards; hopefully it won't be *that* bad
and I will be able to implement some extra features before the
evaluation.
Oh, and before I forget, my awesome mentor Scott is writing some Ruby
bindings for the library [3], which at the moment are mostly in-sync
with all the new functionality I've added. Those will come in handy if
you want to try out the new features of Libgit2 with a more friendly
interface... as friendly as Ruby can be, that is. ;/
Thanks for your time, I'm looking forward to your input and I promise
I'll be much more active on this list from now on.
Cheers,
Vicent Martí
http://www.bellverde.org
[1]: http://repo.or.cz/w/libgit2.git
[2]: http://github.com/tanoku/libgit2-gsoc2010
[3]: http://github.com/schacon/ribbit
next reply other threads:[~2010-05-27 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 16:25 Vicent Marti [this message]
2010-05-27 17:46 ` Libgit2 on the Summer of Code Ilari Liusvaara
2010-05-27 18:05 ` Shawn O. Pearce
2010-05-27 18:22 ` Alex Riesen
2010-06-02 18:42 ` Junio C Hamano
2010-05-27 18:35 ` Ilari Liusvaara
2010-05-28 0:15 ` Vicent Marti
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=AANLkTil-M3kQGbRZIacItlwr37Lf3lso7FspftLr43_F@mail.gmail.com \
--to=tanoku@gmail.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@gmail.com \
/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).