From: Michael Schubert <schu@schu.io>
To: Jeff King <peff@peff.net>
Cc: "Thomas Rast" <trast@inf.ethz.ch>,
git@vger.kernel.org, "Shawn Pearce" <spearce@spearce.org>,
"Jakub Narebski" <jnareb@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>,
"Paul Mackerras" <paulus@samba.org>,
"Carlos Martín Nieto" <cmn@elego.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"David Michael Barr" <davidbarr@google.com>,
"Ramkumar Ramachandra" <artagnon@gmail.com>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
"Vicent Marti" <vicent@github.com>
Subject: Re: Google Summer of Code 2013 (GSoC13)
Date: Wed, 20 Feb 2013 20:48:07 +0100 [thread overview]
Message-ID: <51252877.5000808@schu.io> (raw)
In-Reply-To: <20130218174239.GB22832@sigill.intra.peff.net>
On 02/18/2013 06:42 PM, Jeff King wrote:
>
> I will do it again, if people feel strongly about Git being a part of
> it. However, I have gotten a little soured on the GSoC experience. Not
> because of anything Google has done; it's a good idea, and I think they
> do a fine of administering the program. But I have noticed that the work
> that comes out of GSoC the last few years has quite often not been
> merged, or not made a big impact in the codebase, and nor have the
> participants necessarily stuck around.
>
> And I do not want to blame the students here (some of whom are on the cc
> list :) ). They are certainly under no obligation to stick around after
> GSoC ends, and I know they have many demands on their time. But I am
> also thinking about what Git wants to get out of GSoC (and to my mind,
> the most important thing is contributors).
Speaking of libgit2:
Git provided the libgit2 project with a slot each of the last three GSOC.
The contributions made by the former students (Disclaimer: one of them
speaking) have been quite important for libgit2 and all three students
are still involved. Each project was an important push towards building
a new, feature complete Git library.
Thank you!
http://libgit2.github.com
next prev parent reply other threads:[~2013-02-20 20:03 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:23 Google Summer of Code 2013 (GSoC13) Thomas Rast
2013-02-18 17:42 ` Jeff King
2013-02-18 18:44 ` Ramkumar Ramachandra
2013-02-18 18:58 ` Jeff King
2013-02-18 19:45 ` Ramkumar Ramachandra
2013-02-18 19:57 ` Jonathan Nieder
2013-02-18 20:03 ` Thomas Rast
2013-02-19 7:51 ` Ramkumar Ramachandra
2013-02-18 21:13 ` Jeff King
2013-02-19 9:00 ` Ramkumar Ramachandra
2013-02-18 19:45 ` Thomas Rast
2013-02-18 20:01 ` Jens Lehmann
2013-02-18 22:32 ` Junio C Hamano
2013-02-19 7:08 ` Ramkumar Ramachandra
2013-02-19 7:25 ` Jonathan Nieder
2013-02-19 8:12 ` Ramkumar Ramachandra
2013-02-19 8:41 ` Thomas Rast
2013-02-19 16:29 ` Junio C Hamano
2013-02-19 16:39 ` Thomas Rast
2013-02-19 7:31 ` Junio C Hamano
2013-02-19 8:22 ` Ramkumar Ramachandra
2013-02-19 16:32 ` Junio C Hamano
2013-02-18 19:34 ` Jonathan Nieder
2013-02-18 20:02 ` Jens Lehmann
2013-02-20 6:17 ` Christian Couder
2013-02-18 20:44 ` Ramkumar Ramachandra
2013-02-18 21:07 ` Jeff King
2013-02-18 22:37 ` Junio C Hamano
2013-02-18 21:11 ` Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13)) Jonathan Nieder
2013-02-19 1:23 ` Duy Nguyen
2013-02-18 20:55 ` Google Summer of Code 2013 (GSoC13) Jeff King
2013-02-18 23:03 ` Jonathan Nieder
2013-02-20 6:50 ` Shawn Pearce
2013-02-20 12:07 ` Christian Couder
2013-02-20 12:26 ` Matthieu Moy
2013-02-21 15:41 ` Thomas Rast
2013-02-20 19:48 ` Michael Schubert [this message]
2013-02-21 14:29 ` Carlos Martín Nieto
2013-02-25 9:12 ` Florian Achleitner
2013-02-25 17:44 ` Junio C Hamano
2013-02-18 17:46 ` Thomas Rast
2013-02-18 18:02 ` Ronan Keryell
2013-02-18 19:48 ` Thomas Rast
2013-02-18 18:13 ` Ramkumar Ramachandra
2013-02-18 19:53 ` Thomas Rast
2013-02-19 1:17 ` Duy Nguyen
2013-02-26 4:59 ` Jaseem Abid
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=51252877.5000808@schu.io \
--to=schu@schu.io \
--cc=Jens.Lehmann@web.de \
--cc=artagnon@gmail.com \
--cc=christian.couder@gmail.com \
--cc=cmn@elego.de \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=t.gummerer@gmail.com \
--cc=trast@inf.ethz.ch \
--cc=vicent@github.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).