git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Matthieu Moy" <Matthieu.Moy@imag.fr>,
	"Jeff King" <peff@peff.net>, "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 Barr" <b@rr-dav.id.au>,
	"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 23:25:12 -0800	[thread overview]
Message-ID: <20130219072512.GI19757@elie.Belkin> (raw)
In-Reply-To: <CALkWK0=s4XX0mmUTAcNBHyqdrryhMYvhtrNZCFFccJJBUUVdUg@mail.gmail.com>

Ramkumar Ramachandra wrote:

> The short undiplomatic version of that is that our mentors suck (I'm
> not pointing fingers, but that's what I infer from failing projects).

Hold on a second.  I'm not remembering such a grim outcome with 100%
failure from prior summers of code as you're describing.  Before I
start beating myself up, I guess I'd like a little more information
--- is there some specific project or statistic that you're thinking
of that brings you to that conclusion?

[...]
> I propose that we have one thread for every proposal where we can all
> discuss the implementation outline- this will serve as authoritative
> source of information for students, and for picking mentors (the
> people who contribute most to the discussion).  Students should be
> matched with mentors on an individual basis.

How is that different from what happened in previous summers where
students made proposals, received feedback, and were accepted and
matched to mentors or rejected based on how the discussion went?

Jonathan

  reply	other threads:[~2013-02-19  7:25 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 [this message]
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=20130219072512.GI19757@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=Matthieu.Moy@imag.fr \
    --cc=artagnon@gmail.com \
    --cc=b@rr-dav.id.au \
    --cc=christian.couder@gmail.com \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 \
    /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).