Google Summer of Code 2012 for Students
- Remember name, email, and a title for the project!
- Describe what will be delivered in code by the end of the project.
- Describe prior experience with programming.
- If applicable, supply a code example that shows some relation to the project proposal.
- List week-by-week milestones.
- Plan for any hardware or software needed (See Student Resources below)
- Students must have usable code by the midpoint of the Summer of Code work period.
- Students must have a schedule for their project that encompasses the entire work period.
- Students must maintain weekly (at least) contact with a mentor and/or the project coordinator (Justin Sherrill) though the project period.
- Don't plan on working another job during this time frame.
- Report weekly on progress either on a page on this website or by email to firstname.lastname@example.org. This is in addition to mentor contact.
- Plan carefully! Running out of time kills projects more than anything else.
- Development accounts on leaf.dragonflybsd.org are available. A public RSA or DSA key will be needed for an account. Send the key along with your desired account name to email@example.com.
- Individual Git repositories can be set up on leaf; see the MOTD on login for instructions.
- Our mailing lists
- On IRC: #dragonflybsd on EFNet.
- This Wiki: documentation of progress and ideas.
- Google SoC 2012 FAQ
- Google SoC 2012 timeline
Main DragonFly/SoC2012 page