|Version 8 (modified by hgolden, 3 years ago)|
Haskell.org's Google Summer of Code 2010 Project
This wiki is for organizing our participation, keeping track of the projects, tasks, and publishing news.
Potential mentors and student applicants can (and should) suggest projects using the links below. However, don't forget that, once you find something you are interested in, you will also need to apply directly to Google.
To edit pages, if you don't already have a trac login, you will need to register one. (See buttons top right)
For real-time discussion, join the IRC channel #haskell-soc on irc.freenode.net:6667.
- 2010-01-31: Haskell.org starts preparing for SoC 2010
Want to earn $5,000 USD for 3 months work hacking in Haskell? Go to our ideas page, browse around, and write up a proposal for something you would like to work on. You must be available to work basically full-time for the months of June to August (inclusive). Proposals are competitive against other students.
The deadline for submitting your application to Google is 7th April 2010, so it is a good idea to start working on it now.
- Google Summer of Code 2010 Home
- Google SoC 2010 FAQ
- Google SoC 2010 Timeline
- Google Summer of Code Wiki Knowledge Base
- People2010 - People interested in the project.
- Student application template for haskell.org projects
Mentors and Anyone else:
Got any good ideas for coding projects, but no time to work on them yourself? Add it into the database!
We have started collecting proposal idea on reddit. Use these for inspiration.
Or do you feel you could be either a primary or backup mentor for a student project in an area of your interest, even if it isn't a project you defined yourself? We need willing members of the community to foster the new student talent, so sign up on the People2010 page if you would like to be involved. Obviously you will need Haskell coding experience, but also be able to advise on time management, strategies for gaining a userbase and keeping them happy, ways of interacting with the wider Haskell community, and so on.
We have a list of stale proposals from previous years:
Take a look and if your favourite project is on the list then change it's priority and add a comment giving an explanation.
Tickets <= #86 were proposals from 2006. ome of those ideas are still good, but some might have been completed already. Tickets t: #1102 <= t <= #1131 were proposals from 2007. Items from #1429 upwards were new for 2008 and 2009.
Add some more! (We have disabled anonymous ticket creation to stop spam, so you will need to register a login.)
Students can often find it difficult to pitch a proposal just right for the time available. Mentors (or anybody else with experience) should add comments to proposals, like: off-topic, too easy, too hard, too vague. Please also give suggestions for improvement, helping to tighten-up and clarify what would be cool about the project.
We will probably try to have a backup mentor for every project in the final allocation, so feel free to put yourself down for a proposal, even if you might not be confident enough to be lead mentor.