GSoC proposal guidelines: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
No edit summary
Line 5: Line 5:
* Name.
* Name.
* Email address we can reach you at.
* Email address we can reach you at.
* Summary of proposed development work along with a time line of development
* Name and email address of your academic advisor at your school.
** Please include project mile stones and anticipated delivery dates
* Name of project
* Goal of project
* Sketch the technical approach that you intend to take and point out any relevant and pre-existing code segments you will use.
* Provide a time line with milestones of your expected development progress


In addition you might like to include the following information to help us assess your application,
In addition you might like to include the following information to help us assess your application,
Line 12: Line 15:
* Please tell us about yourself (technical background, open source contributions, etc).
* Please tell us about yourself (technical background, open source contributions, etc).
* What are you studying?
* What are you studying?
* What do you intend to do in your proposed project?
* Why are you the right person for the proposed project?
* Why are you the right person for the proposed project?
* Have you built VTK (or ParaView if appropriate)?
* Have you built VTK (or ParaView if appropriate)?
* Have you submitted a small patch to VTK's gitlab for review and provided a link? /* Not required --[[User:DaveDemarle|DaveDemarle]] ([[User talk:DaveDemarle|talk]]) 11:42, 18 March 2015 (EDT) This is nice to do but not a requirement, we are revising VTK's contribution path right now anyway. */
* Have you submitted a small patch to VTK's gitlab for review and provided a link? /* Strongly recommended by not an absolute requirement. */
* How many hours per week do you intend to work on the project?
* 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?
* Do you have any other commitments during the summer that will affect your start date, end date or compete for your coding attention? /* Google intends GSOC to be a full time summer job, mentors must enforce a high level of involvment with VTK. */
* 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?
* 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?
* 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?

Revision as of 16:00, 26 January 2016

Student Proposal Guidelines

We do not require a specific format, but the following information would be useful to us. They must be submitted through Melange

  • Name.
  • Email address we can reach you at.
  • Name and email address of your academic advisor at your school.
  • Name of project
  • Goal of project
  • Sketch the technical approach that you intend to take and point out any relevant and pre-existing code segments you will use.
  • Provide a time line with milestones of your expected development progress

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?
  • 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 gitlab for review and provided a link? /* Strongly recommended by not an absolute requirement. */
  • How many hours per week do you intend to work on the project?
  • Do you have any other commitments during the summer that will affect your start date, end date or compete for your coding attention? /* Google intends GSOC to be a full time summer job, mentors must enforce a high level of involvment with VTK. */
  • 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.