GSoC 2010 report

flacjacket edited this page Mar 6, 2012 · 2 revisions
Clone this wiki locally

GSoC 2010 Report

Information about the 2010 Google Summer of Code and SymPy

You can watch the progress during the summer at http://planet.sympy.org/

Details

student mentor mentoring organisation blog report proposal
Addison Cugini Brian Granger PSU http://addisoncugini.blogspot.com/ GSoC-2010-Quantum-Computation-Report  
Christian Muise Ondřej Čertík PSF http://haz-tech.blogspot.com/search/label/sympy GSoC-2010-Supercharging-Assumptions-Report  
Aaron Meurer Mateusz Paprocki PSF http://asmeurersympy.wordpress.com/ GSoC-2010-Risch-Integration-Report GsoC-2010-Application-Aaron-Meurer
Matthew Curry Brian Granger PSF http://mattjcurry.blogspot.com/ GSoC-2010-Symbolic-QMReport  
Øyvind Jensen Andy Terrel PSF http://ojensen.wordpress.com/ GSoC-2010-Code-Generation-Report  

Old info

Older information follows:

Introduction

SymPy is going to participate, the same way as in 2007 (see GSoC-2007-Report), 2008 (see GSoC-2008-Report), and 2009 (see GSoC-2009-Report).

Now it's time to get involved in the project - sign up to the SymPy mailinglist, try to fix issues, send patches, simply let us know about yourself.

You don't have to be an expert in Python or other technologies. All we require is that you work on your project as your main job over the summer. If you work hard, we'll help you with everything, e.g. to improve your Python skills and to learn how to work with git, how to send patches, etc. We also require that you blog at least once a week about what you do.

We hope, that you will continue contributing to SymPy even after the summer ends - this is of course not a requirement, but if we had to choose between two applicants, one delivering excellent results for 2 months and then stops, the other one also working hard during the summer (maybe not being as good as the first one), but staying with SymPy after the summer, we prefer the latter, as this helps SymPy more in the end -- but as said before, this is not a requirement, just our wish (see also Google's goals and the Python Software Foundation's expectations wiki).

We encourage you to read the GSoC 2007 and 2008 students reports (see the wiki link above) and feel free to ask them directly for their experience - either on the mailinglist, or privately.

Ideas list

On our public wiki: GSoC-2010-Ideas

Feel free to discuss other ideas on our mailinglist.

How to apply

Sometime in March Google will open applications for students as described on the official timeline, the deadline will be March 29-April 9. See the GSoC Page for an official timeline. If SymPy is accepted as an organization, apply to it. Otherwise please apply directly to mentorship organizations, you can apply to anyone you want, in 2007 it was Python Software Foundation (PSF), Portland State University and the Space Telescope Science Institute that students were successful at, in 2008 it was PSF, and in 2009 is was PSF and Portland State University (PSU). The applications at each organization will be judged and the best ones will be selected (according to the number of slots that Google assigns to each organization).

Informally however, it's good to get involved with the SymPy project before, so that we can help you write a good application and select a good topic, that fits you and us well (and that has a good chance of succeeding). We do require that you submit at least one patch that passes review to become accepted.

Ondřej's note: if you want me to proof read your appliction (recommended:), send it to me before you send it to PSF or other orgs.

Links

GSoC 2010 FAQ: http://code.google.com/opensource/gsoc/2010/faqs.html

Main GSoC 2010 site: http://code.google.com/soc/

Other GSoC 2010 site (where the applications will go): http://socghop.appspot.com/