ITK Google Summer of Code/2013
Project ideas for the Google Summer of Code 2013
Guidelines
Students
These ideas were contributed by developers and users of ITK. If you wish to submit a proposal based on these ideas you should contact the community members identified below to find out more about the idea, get to know the community member that will review your proposal, and receive feedback on your ideas.
The Google Summer of Code program is competitive, and accepted students will usually have thoroughly researched the technologies of their proposed project, been in frequent contact with potential mentors, and ideally have submitted a patch or two to fix bugs in their project (through Gerrit). Kitware makes extensive use of mailing lists, and this would be your best point of initial contact to apply for any of the proposed projects. The mailing lists can be found on the project pages linked in the preceding paragraph. Please see GSoC proposal guidelines for further guidelines on writing your proposal.
Adding Ideas
When adding a new idea to this page, please try to include the following information:
- A brief explanation of the idea
- Expected results/feature additions
- Any prerequisites for working on the project
- Links to any further information, discussions, bug reports etc
- Any special mailing lists if not the standard mailing list for ITK
- Your name and email address for contact (if willing to mentor, or nominated mentor)
Project Ideas
Project page, mailing lists, dashboard.
Project: X
Brief explanation: This is a placeholder for a project description.
Expected results: Good stuff.
Prerequisites: Experience in C++, some experience with lolcats.
Mentor: Matt McCormick (matt dot mccormick at kitware dot com).
