From: Jeff King <peff@peff.net>
To: Thomas Rast <tr@thomasrast.ch>
Cc: git@vger.kernel.org
Subject: Re: [RFH] hackday and GSoC topic suggestions
Date: Sat, 8 Feb 2014 13:55:20 -0500 [thread overview]
Message-ID: <20140208185519.GA26306@sigill.intra.peff.net> (raw)
In-Reply-To: <8738jtmomb.fsf@thomasrast.ch>
On Sat, Feb 08, 2014 at 07:43:40PM +0100, Thomas Rast wrote:
> Jeff King <peff@peff.net> writes:
>
> > On a similar note, the GSoC application deadline is Feb 14th. I am
> > happy to be admin again and put together the application, but we will
> > need an idea page. I'll set up a page to collect them, but in the
> > meantime, please dump any ideas/discussion in this thread.
>
> Sorry for being so procrastinative :-(
>
> I suggest we make it a rule that old projects cannot be proposed from
> year to year.
I would very much agree with that. There are projects that I have posted
multiple years, and nobody ever selects them. I should take that as a
hint that they are not appealing to students for whatever reason, and
are probably just clogging up the ideas list.
I'd make an exception for somebody who wants to substantially rework the
proposal in an attempt to make it more appealing, or who has a reason
why it is being re-proposed (e.g., we had student interest, but we ended
up not selecting it due to running out of slots or something). But those
should be the exception.
-Peff
next prev parent reply other threads:[~2014-02-08 18:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 22:57 [RFH] hackday and GSoC topic suggestions Jeff King
2014-02-06 9:10 ` Christian Couder
2014-02-06 9:51 ` Matthieu Moy
2014-02-13 8:50 ` Jeff King
2014-02-13 9:28 ` Christian Couder
2014-02-13 9:55 ` David Kastrup
2014-02-08 18:43 ` Thomas Rast
2014-02-08 18:55 ` Jeff King [this message]
2014-02-08 19:03 ` Thomas Rast
2014-02-16 14:42 ` Duy Nguyen
2014-02-16 15:29 ` Thomas Rast
2014-02-11 18:57 ` Junio C Hamano
2014-02-11 19:38 ` Junio C Hamano
2014-02-13 8:37 ` Jeff King
2014-02-13 8:41 ` Jeff King
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=20140208185519.GA26306@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tr@thomasrast.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 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.