From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	"Luiz Fernando N. Capitulino" <lcapitulino@gmail.com>,
	Carlos Rica <jasampler@gmail.com>
Subject: Re: Google Summer of Code 2007 progress report / summary
Date: Sun, 2 Sep 2007 23:42:01 -0400	[thread overview]
Message-ID: <20070903034201.GP18160@spearce.org> (raw)
In-Reply-To: <200709030309.30996.jnareb@gmail.com>

Jakub Narebski <jnareb@gmail.com> wrote:
> How it goes with Google Summer of Code git projects:
> builtinification and libification? Which parts are
> done, which parts are worked on?

Heh.  You caught me literally as I was drafting the roundup.  ;-)

The 2007 version of Google Summer of Code[*1*] ended on August 20th.
For those who may be new to the list, Git participated this year
in Google Summer of Code with two successful student projects:

  Shell script to C builtin conversions
    Student: Carlos Rica
	Mentor:  Johannes Schindelin

  Libification
    Student: Luiz Capitulino
    Mentor:  Shawn Pearce

In addition to paying two students to work on Git for the entire
summer Google also donated $1000 USD to our community.  As Git has
no legal entity to receive or make use of these funds we directed
the full $1000 donation to the Free Software Foundation.

A good part of Carlos Rica's work is in Git 1.5.3 and brought us a
C based version of git-tag, as well as a comprehensive test suite
for git-tag and its various modes of operation.  Additionally Carlos
fixed a few bugs and improved some of the internal code to make a
C based version of git-commit easier to develop.  Carlos has more
recently been working on a C based version of git-reset, which will
hopefully be in the next version of Git (1.5.3.1? 1.5.4?).

Luiz Capitulino has found and submitted a few bug fixes to Git
1.5.3, but the majority of his work on creating an application
level library is still unmerged and can be found on repo.or.cz[*2*].
Luiz developed a C and Python log API and announced it on list[*3*]
near the end of July.  During August Luiz also worked with Marco
Costalba to modify qgit4 to use Luiz's log API.  This work is
currently stalled as Luiz has shifted his attention to expanding
and rebasing the work that Nico and I had done for pack v4 onto
current Git 1.5.3.  Luiz also tried to port StGIT to use this new
Python API but determined that StGIT needs more functions than the
API currently offers.  It may be interesting if someone picks up
this API work and continues it further.

I would like to thank our two students for their excellent work,
but also Brian Gernhardt, Johannes Schindelin, Martin Langhoff,
Martin Waitz, Petr Baudis, and Sam Vilain for helping us to review
student applications and for volunteering to mentor students.


*1* http://code.google.com/soc/2007/
*2* http://repo.or.cz/w/git/libgit-gsoc.git
*3* http://article.gmane.org/gmane.comp.version-control.git/53433

-- 
Shawn.

     prev parent reply	other threads:[~2007-09-03  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-03  1:09 Google Summer of Code 2007 progress report / summary Jakub Narebski
2007-09-03  3:42 ` Shawn O. Pearce [this message]

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=20070903034201.GP18160@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jasampler@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=lcapitulino@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

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).