GSoC proposal guidelines: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
DaveDemarle (talk | contribs) No edit summary |
DaveDemarle (talk | contribs) |
||
| Line 1: | Line 1: | ||
== Student Proposal Guidelines == | == Student Proposal Guidelines == | ||
We do not require a specific format, but the following information would be useful to us. They must be submitted through [ | We do not require a specific format, but the following information would be useful to us. They must be submitted through the [https://developers.google.com/open-source/gsoc/ GSOC] web site. You are free to base your proposal from our one of our suggested topics, or create your own. We recommend that you ask the mailing list and/or the specific mentor listed for a topic for guidance on how to make a great proposal. | ||
=== Requirements === | |||
* Name. | * Name. | ||
| Line 10: | Line 12: | ||
* Provide a timeline with milestones of your expected development progress. | * Provide a timeline with milestones of your expected development progress. | ||
* Do you have any other commitments during the summer that will affect your start date, end date or compete for your coding attention? /* GSOC is intended to be a full time summer job, mentors will enforce a high level of involvement with VTK. */ | * Do you have any other commitments during the summer that will affect your start date, end date or compete for your coding attention? /* GSOC is intended to be a full time summer job, mentors will enforce a high level of involvement with VTK. */ | ||
=== Suggestions === | |||
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 16: | Line 20: | ||
* What are you studying? | * What are you studying? | ||
* 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 | * Have you built VTK (or a higher level project that uses VTK) before? | ||
* Have you submitted a small patch to VTK's gitlab for review and provided a link? /* Strongly recommended by not an absolute requirement. */ | * 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? | ||
| Line 23: | Line 27: | ||
* 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. | * 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. | * IRC, instant messenger/alternate contact details. | ||
* Provide the name and email address of your academic advisor at your school who we can contact if we | * Provide the name and email address of your academic advisor at your school who we can contact if we have questions about your background. | ||
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. | 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. | ||
Revision as of 02:11, 9 February 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 the GSOC web site. You are free to base your proposal from our one of our suggested topics, or create your own. We recommend that you ask the mailing list and/or the specific mentor listed for a topic for guidance on how to make a great proposal.
Requirements
- Name.
- Email address we can reach you at.
- Name of project
- Goal of project
- Sketch the technical approach that you intend to take. Point out relevant code in VTK that you think you will use and/or extend.
- Provide a timeline with milestones of your expected development progress.
- Do you have any other commitments during the summer that will affect your start date, end date or compete for your coding attention? /* GSOC is intended to be a full time summer job, mentors will enforce a high level of involvement with VTK. */
Suggestions
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 a higher level project that uses VTK) before?
- 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 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.
- Provide the name and email address of your academic advisor at your school who we can contact if we have questions about your background.
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.
