GSoC proposal guidelines

From KitwarePublic
Revision as of 08:13, 18 March 2014 by Marcus.hanwell (talk | contribs) (Added a few more points that we would like to see)
Jump to navigationJump to search

Student Proposal Guidelines

We do not require a specific format, but the following information would be useful to us.

  • Name.
  • Email address we can reach you at.

In addition you might like to include the following information to help us assess your application,

  • Please tell us about yourself (technical background, open source contributions, etc).
  • What are you studying?
  • What do you intend to do in your proposed project?
  • Why are you the right person for the proposed project?
  • Have you built VTK (or ParaView if appropriate)?
  • Have you submitted a small patch to VTK's Gerrit for review, provided a link?
  • How many hours per week do you intend to work on the project?
  • Do you have any other commitments during the summer that we should know about?
  • How familiar are you with the programming language(s), technologies and software projects you intend to work with? Have you used the software before, have you read the source and have you ever submitted patches to the project?
  • Are you comfortable working remotely under a mentor who may not be in the same time zone as you? Have you ever worked in a similar way before? How will you communicate with your mentor, keep them updated of progress/work through problems?
  • If your native language is not English, are you comfortable working closely with a mentor whose native language is English? It is also possible that we could pair you with a mentor who has the same native language.
  • IRC, instant messenger/alternate contact details.

After you have written your proposal you should get it reviewed. Do not rely on the mentors to do it for you via the web interface, ask a colleague or developer for feedback.