Menu

- Learn
- Documentation
  - Language Reference
  - Library Reference
  - Command-line Reference
  - Feature Overview
  - Articles
- Packages
- Community
  - Blog
  - Orgs using D
  - Twitter
  - Forums
  - IRC
  - Wiki
  - GitHub
  - Issues
  - Foundation
  - Donate
- Resources
  - Books
  - Tutorials
  - Tools
  - Editors
  - IDEs
  - Visual D
  - Acknowledgments
  - D Style
  - Glossary
  - Sitemap

Search
Report a bug
If you spot a problem with this page, click here to create a Bugzilla issue.
Improve this page
Quickly fork, edit online, and submit a pull request for this page. Requires a signed-in GitHub account. This works well for small changes. If you'd like to make larger changes you may want to consider using a local clone.

# GSoC2012

## Application template for the 2012 Google Summer of Code program

### Personal Details

- Name
- Email
- Personal website
- Skype/GTalk ID
- IRC nickname
- Phone number

### Skills

- School
- Years completed
- Anticipated graduation
- Academic performance (list relevant coursework taken and grades)
- Programming experience level
- D experience level
- If you participated to past D projects or others (preferably open source), include a brief description of each
- Also list any specific skills in the specific project area (classes taken, research conducted, blogs and publications etc.)

References (names and emails of up to four relevant professors, employers or collaborators)

### Your Project

- One-sentence elevator pitch
- Detailed description
- How many hours per week do you expect to spend on the project?
- Your current progress on the idea—e.g. research, gathering information, concrete work if applicable
- Anticipated impact—if you implemented your idea to perfection, how will it have made the world a better place?
- Anticipated challenges
- Potential mentors

### Major Milestones

Put together a broad project plan. What are the major deliverables that would mark progress in your work, and when do you plan on delivering them? For example:

- 06/01 Revise project plan with mentor, discuss strategy of approach
- 06/15 Mocks, small prototype available, finish research on the topic, begin coding
- 07/15 First reviewable code submitted implementing X, Y, and Z
- 08/15 Feature complete, review overall progress
- 09/01 Rule the world

Good luck!

Copyright © 1999-2017 by the D Language Foundation | Page generated by Ddoc on Thu Mar 9 17:49:30 2017