Changes between Initial Version and Version 1 of StudApply2011


Ignore:
Timestamp:
Mar 19, 2011 12:15:23 AM (4 years ago)
Author:
dterei
Comment:

copied from 2010

Legend:

Unmodified
Added
Removed
Modified
  • StudApply2011

    v1 v1  
     1= Student application template = 
     2 
     3For this year's Google Summer of Code, Haskell.org is particularly keen 
     4to see proposals for work on libraries, compilers, and tools, that is, 
     5infrastructure to support the growth of the language, rather than (say)  
     6applications that merely use Haskell. 
     7 
     8For reference, past successful project proposals can be seen from  
     9[http://code.google.com/soc/2006/haskell/about.html 2006], [http://code.google.com/soc/2007/haskell/about.html 2007] and [http://code.google.com/soc/2008/haskell/about.html 2008]. 
     10 
     11Click on the project names to see some good models for how to write 
     12a winning proposal. 
     13 
     14In your application, try to tell us as much as possible about yourself, 
     15and what you want to do.  It is much easier to judge a long proposal 
     16than a short one.  Sell yourself. 
     17 
     18[http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-student-applicants Official Google instructions for submitting your proposal] 
     19 
     20= Before you apply = 
     21 
     22Consider the following caveats before you apply: 
     23 * 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. 
     24 
     25 * 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. 
     26 
     27 * 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. 
     28 
     29= Questions = 
     30 
     31 * What is the goal of the project you propose to do? 
     32 
     33 * In what ways will this project benefit the wider Haskell community? 
     34 
     35 * Can you give some more detailed design of what precisely you intend to 
     36   achieve? 
     37 
     38 * What deliverables do you think are reasonable targets? 
     39   Can you outline an approximate schedule of milestones? 
     40 
     41 * What relevant experience do you have?  e.g. Have you coded anything 
     42   in Haskell?  Have you contributed to any other open source software? 
     43   Been studying advanced courses in a related topic? 
     44 
     45 * In what ways do you envisage interacting with the wider Haskell 
     46   community during your project?  e.g. How would you seek help on 
     47   something your mentor wasn't able to deal with?  How will you get others 
     48   interested in what you are doing? 
     49 
     50 * Why do you think you would be the best person to tackle this project?