Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Show that you have thought about how you will spend your time by supplying an expected timeline for each week during the coding period with milestones.
  • How many hours per day you intend to spend working on the project? We expect this to be your only job during the coding period and require that you spend 40 hours per week on the project.
  • Be honest about any other commitments you may have over the coding period.
  • Did you apply to GSoC last year to take part in another internship program? Were you successful? If yes, tell us about your project and how it went.

And finally, a few ' don'ts':

  • Don't enter a placeholder proposal. It gives a bad impression of poor time management, lack of real enthusiasm and poor organisation. We pass over them and concentrate on the rest.
  • Don't just repeat the information shown on our Ideas List. Refer to it but then use your own ideas to show how you would tackle the problem and any challenges you might face.
  • Don't wait until the last minute to submit. Mentors may have questions and comments and you might too. Submit in plenty time so you can respond and update your proposal with improvements.
  • Don't submit and think that's it until acceptance. If a mentor asks a question, please respond in good time. Failure to respond indicates lack of interest and commitment and you will miss out on the opportunity to increase your chances of acceptance by improving your proposal.
  • Don't give the impression that you are applying because someone told you it was a good idea, for example, your tutor. It's ok to say that it was recommended to you but go on and say why you like the idea, how you feel about working on one of our projects and what you feel you will get out of the experience.

...