Changes between Version 1 and Version 2 of StudApply2008


Ignore:
Timestamp:
Mar 3, 2008 1:33:17 PM (6 years ago)
Author:
malcolm.wallace@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • StudApply2008

    v1 v2  
    66applications that merely use Haskell. 
    77 
    8 For reference, the successful project proposals in 2006 can be seen 
    9 [http://code.google.com/soc/2006/haskell/about.html here]. 
     8For reference, the successful project proposals in 2007 can be seen 
     9[http://code.google.com/soc/2007/haskell/about.html here]. 
    1010Click on the project names to see some good models for how to write 
    1111a winning proposal. 
     
    1616 
    1717[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] 
     18 
     19= Before you apply = 
     20 
     21Consider the following caveats before you apply: 
     22 * 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. 
     23 * 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. 
     24 * 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. 
    1825 
    1926= Questions = 
     
    4047 * Why do you think you would be the best person to tackle this project? 
    4148 
    42 = Caveats = 
    43  
    44  * Please note that Google Summer-of-Code projects are a full (day-) time 
    45    job. 
    46  
    47  * A positive mid-term evaluation is only possible if code has 
    48    been committed by that time.  Make sure your schedule allows for this. 
    49