git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <christian.couder@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	git@vger.kernel.org
Subject: Re: Git and GSoC 2013
Date: Thu, 28 Mar 2013 13:07:09 -0400	[thread overview]
Message-ID: <20130328170709.GA8256@sigill.intra.peff.net> (raw)
In-Reply-To: <7vtxnvv5gx.fsf@alter.siamese.dyndns.org>

On Thu, Mar 28, 2013 at 09:45:02AM -0700, Junio C Hamano wrote:

> It is preferrable if the decision were accompanied with a concrete
> plan for us to prepare our mentoring capability better (if we want
> to participate in future GSoC, that is), but I think it is a
> separate issue, and I suspect that it is too late for this year's.

I agree with this. I do think we should participate again, and I think
we should try to address the issues I brought up (and you mentioned
in your email) about project size and community involvement.

My email was meant to be a "maybe it's not too late if people really
want to work on the project ideas page". But I haven't seen anything
happening there, and we really are running right up to the deadline[1].
I think at this point it makes sense to wait a year and try to approach
it sooner next year.

-Peff

[1] I know my email didn't give much time for action; the deadline snuck
    up on me, too.

  reply	other threads:[~2013-03-28 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 18:34 Git and GSoC 2013 Jeff King
2013-03-27 18:52 ` Jonathan Nieder
2013-03-27 22:15   ` Christian Couder
2013-03-28 16:45     ` Junio C Hamano
2013-03-28 17:07       ` Jeff King [this message]
2013-03-28 20:39       ` Christian Couder
2013-03-29  4:57         ` Junio C Hamano
2013-03-28 15:17 ` Ramkumar Ramachandra

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=20130328170709.GA8256@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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 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).