git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: 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>
Subject: Re: Google Summer of Code 2013 (GSoC13)
Date: Mon, 18 Feb 2013 12:42:39 -0500	[thread overview]
Message-ID: <20130218174239.GB22832@sigill.intra.peff.net> (raw)
In-Reply-To: <87ehgd1qq2.fsf@pctrast.inf.ethz.ch>

On Mon, Feb 18, 2013 at 06:23:01PM +0100, Thomas Rast wrote:

> * We need an org admin.  AFAIK this was done by Peff and Shawn in
>   tandem last year.  Would you do it again?

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

As far as merged code, I think part of the problem is that git is fairly
mature at this point. The most interesting projects are of a bigger
scope than a student with no experience in the code base can do in a
summer project. Maybe that means we need to do a better job of breaking
projects down into reasonably sized sub-components. Or maybe it means
the project is hitting a point of diminishing returns for GSoC. I don't
know.

There are a few counterpoints I can think of:

  - Even though not all projects are winners, _some_ are. I see Carlos
    and Ram on the cc list, two people who started as GSoC students and
    stuck around.

  - There is also the angle that even if _Git_ doesn't benefit directly
    from people sticking around, those people may float into other open
    source projects and work on them. Which makes the world a better
    place on the whole.

So I don't know. Those are just some things that have been floating
around in my head. Feel free to ignore or discuss.

But thanks for getting the ball rolling, Thomas. If we are going to do
it, sooner is better, and if we aren't, then we should probably do so
consciously, and not just miss the deadline accidentally. :)

> * We should prepare an "ideas page".  Last year, Peff made one on
> 
>     https://github.com/peff/git/wiki/SoC-2012-Ideas
> 
>   I couldn't edit it there over git access[1], so I made a clone in "my"
>   github wiki:
> [...]
> [1]  That's a bit silly really, since I *can* edit it via the web
> interface.  Peff, perhaps you can get that fixed?

Ugh, I would have to write ruby code to fix that. I'll try to trick
somebody else here into fixing it. :)

> [2]  Unless Peff wants to take it over again?  You could just pull it
> from the git version, it's based on your history.

I think it is as good on your repo as on mine. The kernel.org wiki is
also up, and the github/peff/git one was supposed to be temporary. But I
really hate any wiki that I cannot edit with vim. I guess we need to
have a discussion as a group about where the "official" wiki should
live, and it should go there (I can also put it at github/git/git, which
is a more sane place; but I do not want to compete with kernel.org's
wiki unless there is community consensus that we are moving).

-Peff

  reply	other threads:[~2013-02-18 17:43 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 [this message]
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
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=20130218174239.GB22832@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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=spearce@spearce.org \
    --cc=t.gummerer@gmail.com \
    --cc=trast@inf.ethz.ch \
    /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).