All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: Google Summer of Code 2008
Date: Thu, 28 Feb 2008 01:36:21 -0500	[thread overview]
Message-ID: <20080228063621.GR8410@spearce.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0802262337390.22527@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Tue, 26 Feb 2008, Jakub Narebski wrote:
> 
> > I have just read (via Linux Today news[*1*]) that GSoC 2008 initiative 
> > starts early.  Applications for organizations open March 3 and close 
> > March 12.  Git development community participated in GSoC 2007 with two 
> > projects accepted[*2*]: builtinification and libification.  What do you 
> > think about their results for git? What do you think about participating 
> > in this year GSoC?
> 
> I think that GSoC2007 was quite nice for us.  And with what we learnt, we 
> would do even better in 2008.

I agree.  Unfortunately though it seems only 3 of us out of 855
current subscribers to the git mailing list have anything to say
on the subject in the past couple of days. :-\
 
> However, I simply do not have the time to serve as primary contact.  I am 
> willing to be mentor again, though.

I'd be willing to do it again, as well as mentor a student.  I found it
very interesting last year.
 
> As for projects, I imagine that Gitorrent, further builtinification and 
> Windows support would be good candidates.

Yea, Gitorrent would be cool.  Especially since send-pack is
somewhat heavy on the server's resources and there are some very
popular projects offered in git format (hello Linux kernel!).

I'd love to see new features added to git-gui, but I'm being selfish.
Ditto with jgit and egit, though I think Robin has done a stellar
job with them thus far.  I can still want them to grow.

pack v4 (or maybe v5?! a student could have better ideas then we
have thus far come up with) would also be interesting.

My list could probably go on for a bit.

-- 
Shawn.

  reply	other threads:[~2008-02-28  6:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 22:56 Google Summer of Code 2008 Jakub Narebski
2008-02-26 23:39 ` Johannes Schindelin
2008-02-28  6:36   ` Shawn O. Pearce [this message]
2008-02-28  7:03     ` Jeremy Maitin-Shepard
2008-02-28 10:27       ` Johannes Schindelin
2008-02-28 10:27     ` Johannes Schindelin
2008-02-29 12:04       ` Jakub Narebski
2008-02-29 12:47         ` Julian Phillips
2008-02-29 13:03           ` Johannes Schindelin
2008-03-01  1:37             ` Julian Phillips
2008-03-01  0:31         ` Sam Vilain
2008-03-01  1:03           ` Johannes Schindelin
2008-03-01  5:07             ` Sam Vilain
2008-03-01 23:53         ` Jakub Narebski
2008-03-02 16:05           ` Matthieu Moy
2008-03-02 16:46             ` Jakub Narebski
2008-03-02 18:05               ` Matthieu Moy
2008-03-02 23:04         ` Martin Langhoff
2008-03-02 23:35           ` Johannes Schindelin
2008-02-28 13:59     ` Jonas Fonseca

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=20080228063621.GR8410@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.