----- Forwarded message from Terri Oda <[email protected]> -----

Date: Mon, 10 Mar 2014 01:42:59 -0700
From: Terri Oda <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [Soc2014-mentors] 2014 PSF Application template now available

I've put up the application template for this year:

https://wiki.python.org/moin/SummerOfCode/ApplicationTemplate2014

It may undergo some tweaking if it turns out the wording is unclear,
but this should be pretty stable otherwise.

Things to note:

* Some of the sections are in fact new this year (I'm asking for time
zone and a blog feed url up-front)

* We require all students to submit a code patch as part of their
application.  Ideally, we'd like this to be patch for your sub-org,
fixing an easy bug.  If for some reason that's not workable for your
org, you can give the students alternative instructions (such as a
preset practice problem), but do have them submit a link to some sort
of code sample written for this purpose.

* As in previous years, we will be requiring the students to blog
every 2 weeks.   This is how I (and my fellow org admins, Florian and
Meflin) keep track of student progress, as it's impractical for us to
get involved in 21 development mailing lists.   We use this as an
early warning system for problems, a way for us as org admins to get a
sense of the work we're sponsoring, and a way for us to promote that
work outside of our little GSoC crowd.   This year, I'm in the process
of making arrangements with the PSF to show off the student work to
the wider Python community, and if all goes well they'll also be
aggregated on Planet Python and occasionally some highlights will be
featured on the PSF blog.

* I am really serious about requiring the sub-org name in the title of
the project.  You're going to be able to see all the student
applicants and searching manually through 100 applications to find the
8 that are relevant to you is annoying.  Last year, they gave me an
option to add fields for us to use so I added one so you could sort by
sub-org, but those fields don't show up in the emails google sends out
or in the midterm/final lists, so we need the sub-org name in the
project title anyhow.

* Especially if you're new to GSoC, you may want to read the
recommended proposal guidelines here:
http://en.flossmanuals.net/GSoCStudentGuide/ch008_writing-a-proposal/
And the example proposals:
http://en.flossmanuals.net/GSoCStudentGuide/ch027_proposal-example-1/
http://en.flossmanuals.net/GSoCStudentGuide/ch028_proposal-example-2/

* You should feel free to request any additional information you think
you need!



_______________________________________________
Soc2014-mentors mailing list
[email protected]
https://mail.python.org/mailman/listinfo/soc2014-mentors

----- End forwarded message -----

-- 
    Gael Varoquaux
    Researcher, INRIA Parietal
    Laboratoire de Neuro-Imagerie Assistee par Ordinateur
    NeuroSpin/CEA Saclay , Bat 145, 91191 Gif-sur-Yvette France
    Phone:  ++ 33-1-69-08-79-68
    http://gael-varoquaux.info            http://twitter.com/GaelVaroquaux

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general

Reply via email to