Student application template

For this year's Google Summer of Code, is particularly keen to see proposals for work on libraries, compilers, and tools, that is, infrastructure to support the growth of the language, rather than (say) applications that merely use Haskell.

For reference, past successful project proposals can be seen from 2006, 2007 and 2008.

Click on the project names to see some good models for how to write a winning proposal.

In your application, try to tell us as much as possible about yourself, and what you want to do. It is much easier to judge a long proposal than a short one. Sell yourself.

Official Google instructions for submitting your proposal

Before you apply

Consider the following caveats before you apply:

  • Google Summer-of-Code projects are a full (day-) time job. This means we expect roughly 36 hours per week on your project, during the three months of coding. Obviously we have flexibility, but if your schedule (exams, courses) does not give you this amount of spare time, then maybe you should not apply.
  • Getting paid by Google requires that you meet certain milestones. First, you must be in good standing with the community before the official start of the programme. We suggest you post some design emails to some mailing lists, and get feedback on them, both before applying, and during the "community bonding period" between acceptance and official start. Also, you must have made progress and committed significant code before the mid-term point.
  • We are thinking of requiring accepted students to have a blog syndicated to Planet Haskell, where you will write about your project on a regular basis. This is so that the community at large can be involved and help you. SoC is not a private contract between your mentor and you.


  • What is the goal of the project you propose to do?
  • In what ways will this project benefit the wider Haskell community?
  • Can you give some more detailed design of what precisely you intend to achieve?
  • What deliverables do you think are reasonable targets? Can you outline an approximate schedule of milestones?
  • What relevant experience do you have? e.g. Have you coded anything in Haskell? Have you contributed to any other open source software? Been studying advanced courses in a related topic?
  • In what ways do you envisage interacting with the wider Haskell community during your project? e.g. How would you seek help on something your mentor wasn't able to deal with? How will you get others interested in what you are doing?
  • Why do you think you would be the best person to tackle this project?
Last modified 8 years ago Last modified on Mar 12, 2010 4:09:42 AM