-
Notifications
You must be signed in to change notification settings - Fork 0
application template
This is a template that is highly recommended to follow for your applications for GeomScale GSoD projects.
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.
Technical Writer name:
Technical Writer 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. :
Please list any schedule conflict that will interfere with you treating your proposed GCoD project as a full time job. If you are applying to other positions, or have other commitments, list them.
Main 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 documented, how and when will you do design? 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 GSoD 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 GSoD schedule)
Provide a detailed timeline of how you plan to spend your season.
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 documenting.
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 GSoD, we highly recommend explaining how you will front-load the work before documenting start or work extra early on to build a cushion!
How do you propose to ensure doc is submitted?
How often do you plan to commit? What changes in commit behavior would indicate a problem?