2013-04-24 01:57:17 UTC
As of a couple of days, applications are open. Scikit-learn is a
suborganization of the PSF this year, like in previous years, so you
will apply with PSF as an organzation, specifying that you will work
on scikit-learn. The PSF were kind enough to provide instructions and
a template for the proposals, so you are
invited to peruse them. I am forwarding the specific e-mail here.
I would like to stress that there is a strict requirement for having
contributed some code to scikit-learn, and to blog weekly about your
But most importantly, please discuss your proposal on the mailing
list, the sooner the better. There have been discussions until now,
maybe less active than they should have been, but I hope ideas and
directions have crystallised a bit and we will soon see good
discussion and competitive proposals.
---------- Forwarded message ----------
From: Terri Oda <***@zone12.com>
Date: Mon, Apr 22, 2013 at 7:22 AM
Subject: [Soc2013-general] Student Application Template (Applications
start April 22!)
As hopefully all of you are aware, student applications to GSoC will
be opening April 22 19:00 UTC (tomorrow to me) and closing May 3rd. I
highly recommend that you all submit applications early -- you can
modify them up until the final deadline. Google will not extend the
deadline for any reason, including technical problems with the melange
system (which have been known to happen at the last minute in the
past), so the sooner you can get an application in the better!
We have a template to help you prepare your application with the PSF:
Your sub-organizations may have additional requirements; ask them if
there's any extra information they need from you.
Please note a few things we ask for that are not always required by other orgs:
* We do require students to blog about their projects, so you will
need to set up a GSoC blog for weekly status updates and any other
thoughts you wish to record about your project.
* We do require students to submit a link to some sort of code sample,
preferably a patch to the sub-org to which you are applying. Talk to
your mentors if you're uncertain what would be appropriate.
* Don't forget to put the name of your sub-organization (e.g.
OpenHatch, MNE-Python) into the title of your application.
If you're not sure about how to write a good proposal, ask your
prospective mentors: they're the ones who will be deciding if they
hire you or not, so they get the final word as to what a good proposal
looks like for them.