-
Notifications
You must be signed in to change notification settings - Fork 6
application template
Applications that do not contain at least the minimum information in the template **will not** get a slot.
The best applications run to several pages (10+) if printed, and show considerable thought and planning. The application process is longer this year than it has been in some prior years, so this should not be a problem.
If you have questions about details, contact your mentors first. If you still have choices to make or different possible approaches, explore the most likely ones in your application. The goal of your application is to demonstrate your capability to complete the work of the project over the course of the summer, demonstrate that you’ve given a fair amount of thought to an implementation approach, and plan, as much as possible, for choices that may change the goals or timeline in the application.
Once your draft application has been submitted, you may receive comments from other R mentors, either listed project mentors or others. Please respond to the comments promptly and completely. Being non-responsive before you’ve even been awarded a slot is not a good sign for the success of your proposal.
Project title:
Project short title (30 characters):
URL of project idea page:
Provide a brief (text) biography, and why you think your background qualifies you for this project.
Student name:
Student postal address:
Telephone(s):
Email(s): (make sure to include the email you’ve registered on the google system with, as well as any other good ways to contact you)
Other communications channels: Skype/Google+, etc. :
Institution:
Program:
Stage of completion:
Contact to verify:
Please list any schedule conflict that will interfere with you treating your proposed R GCoC project as a full time job in the summer. If you are applying to other internships, or have other commitments, list them.
Evaluating mentor name and email:
Co-mentor name(s) and email(s): (at least one co-mentor required, who has to be from a different physical institution from the evaluating mentor)
Have you been in touch with the mentors? When and how?
Describe in detail your plan for completing the work. What functions will be written, how and when will you do design, how will you verify the results of your coding? The sub-section headings below are examples only. Each project is different, please make your application appropriate to the work you propose.
Describe perceived obstacles and challenges, and how you plan to overcome them.
The best R GSoC applications tend to be 10+ pages printed. Planning is a key part of a successful project, and demonstrates to the mentors that you are qualified and engaged.
(consult GSOC schedule)
Provide a detailed timeline of how you plan to spend your summer. Don’t leave testing and documentation for last, as that’s almost a guarantee of a failed project.
Make sure to identify what you plan to accomplish in each month of the project. Google has asked organizations to be more directive about milestones. Also be sure to identify what you will accomplish between acceptance and the official start of coding. (Hint: establishing your build environment and researching existing work shouldn’t wait till project start)
What is your contingency plan for things not going to schedule? We understand things change, but how are you planning to address changes and setbacks?
If you have other time commitments that will interfere with GSoC, we highly recommend explaining how you will front-load the work before coding start or work extra early on to build a cushion!
How do you propose to ensure code is submitted / tested?
How often do you plan to commit? What changes in commit behavior would indicate a problem?
Describe the qualification test that you have submitted to you project mentors. If feasible, include code, details, output, and example of similar coding problems that you have solved.