GSoC 2010 Student Template
You are encouraged to start with a draft application of your proposed assignment. The final application has to be submitted to a GSoC website. Feel free to request preliminary feedback of a potential mentor. The earlier matches are made, and project plans are reviewed, the higher the chances of success!
1. About the Student
1.1. Contact/working info
- Name:
- E-mail:
- Telephone:
- Timezone:
- Typical working hours:
- IRC or IM networks/handle(s):
1.2. About you
- Short biography (programming experience, academic work, open source background and other activities that you like to do)
- What does making this project happen mean to you?
- Do you have other commitments during the GSoC period? If yes, what kind of commitments?
- Why are you the right person for this project?
1.3. Past open source experience
Do you have any past experience working in open source projects. If so, tell us about it!
You don't need to write out your life story (we can read your blog if we want that), but we want to know a little about what makes you tick.
2. About the Project
2.1. Project title
If you choose a project from the Ideas List, it might be the same title.
2.2. Project summary
Two or three paragraphs describing your project -- what it means to accomplish and how it will benefit InVesalius.
2.3. Deliverables
It should be possible to break down your project into some bullet points describing particular features or milestones which can be reached individually. Consider that we may wish to roll out the system for testing when at an intermediate stage of completion, and that time estimates might vary, leaving you with more time than you expected or (more likely) a lot less -- some features can be pushed back if you end up short.
2.4. Required deliverables
- ...
- ...
2.5. If time permits
- ...
2.6. Project schedule
Try to break your deliverables into "milestone" points which can be reached in sequence. Block out your estimated schedule of when you'll reach each functional milestone. Don't forgot that real time may change -- leave enough wiggle room for your required features to be completed!
2.7. Participation
We don't just want to know what you plan to accomplish; we want to know how. Briefly describe your work style: how you plan to communicate progress, how many daily commits, how and where you plan to ask for help. (We will tend to favor applicants that demonstrate a clear vision for what it means to be an active participant in our development community)
2.8. Any other info
If there's other relevant information -- UI mockups, references to related projects, a link to your proof of concept code, whatever. There are no specific requirements, but we love to see people who love what they're doing. Show us you're excited about this project and have an interest in the background and are considering how best to make your idea work.
