If you haven't done so already, be sure to visit the Wiki Portal to read about how the wiki works. Especially the Ogre Wiki Overview page.
Personal Details
- Name:
- Email:
- OGRE Forum username:
- GTalk or Skype ID (for IM and voice chats):
Project Proposal
Here you should detail what it is you're proposing to develop. Take a look at our Ideas List to see if there's anything there you fancy tackling - the list is very roughly in preference order. However, feel free to propose an idea of your own, since last time we checked we weren't omnipotent.
Things you need to consider:
- How will this project benefit OGRE users?
- Is this project within the core scope of OGRE? Project proposals which are 'add ons', such as external applications or highly specialised techniques with only a small audience will be less useful than core features.
- Is it realistic to achieve over a summer? Extensions and refinements can happen later of course (this is open source after all), but something self-contained and useful should be achieveable within the time you have available.
Schedule
Set out here a schedule of milestones for your project - be realistic, because if accepted you will be expected to meet them as part of the mentor review process, upon which your student payment depends. You should aim to define a milestone roughly every week.
Do you have any other commitments during the summer? Bear in mind that commitment to the Summer of Code is a full-time one over the few weeks that the programme runs. If you have exams or other commitments, make sure you factor those in to your schedule and plan to catch up later.
Future Extensions
After the summer, how would you envisage the project being extended in the future? No concrete plans are required here, just some ideas of where you might like to take the project later.
Why You're The Person For This Project
Tell us why you think you're the one to tackle this particular project. You'll want to mention your qualifications, development experience, experience working in teams, technical skills (with particular emphasis on C++ and graphics systems), and particularly how long you've been using OGRE for. Existing work with OGRE, and/or active technical discussions in the forums will help your case here. You should definitely provide links to code samples that you've written too, again preferably with OGRE.
Communication skills are just as key in the Google Summer of Code as technical skills - you'll be expected to talk to your mentor and the wider community regularly. Therefore examples of being actively involved in a community (preferably the OGRE forums obviously) will support your application.
Why OGRE?
Tell us a little about why you're choosing to apply to OGRE for the Google Summer of Code.
Contributor Agreement
Please be aware that all OGRE contributors are required to sign the OGRE Contributor License Agreement - this will be a condition of acceptance of your project should your application be accepted.
Anything Else
Feel free to include here any other points you want to make about your application.
Contributors to this page: jacmoe
and
Spacegaier
.
Page last modified on Monday 04 of January, 2010 16:44:15 GMT by jacmoe
.
The content on this page is licensed under the terms of the Creative Commons Attribution-ShareAlike License.
As an exception, any source code contributed within the content is released into the Public Domain.

