TrustedUser
2,147
edits
Difference between revisions of "GSoC Application"
Update to take into account the two intermediate evaluations (instead of one mid-term evaluation in the past)
(Restore introduction) |
(Update to take into account the two intermediate evaluations (instead of one mid-term evaluation in the past)) |
||
| Line 1: | Line 1: | ||
Your application has two important purposes: It should clearly identify the goals of your project, and it should convince us that you are the right person for this task. | Your application has two important purposes: It should clearly identify the goals of your project, and it should convince us that you are the right person for this task. | ||
In particular, your application is your opportunity to show us that you understand what you'll be doing for the task, and to demonstrate that you've spent some time thinking about it, its difficulties, strategies for overcoming these, and have a good estimate of how much time they will take. Based on that, we will ask you a realistic planning for the 12 weeks of GSoC, including the deliverables expected | In particular, your application is your opportunity to show us that you understand what you'll be doing for the task, and to demonstrate that you've spent some time thinking about it, its difficulties, strategies for overcoming these, and have a good estimate of how much time they will take. Based on that, we will ask you a realistic planning for the 12 weeks of GSoC, including the deliverables expected for each intermediate evaluation period and at the end of the GSoC. In order to be complete, we also expect you to make a pull request, for example for a bug fix. The purpose is to ensure you know how to use Git, and that you had a look at our coding conventions. | ||
We don't expect you to produce a perfect application without any help at all. We strongly encourage you to discuss your plans and your application with us while you're preparing it, to ensure your ideas align well with our own thoughts on the tasks, and that your objectives are achievable. It is also the perfect chance to already get to know your potential mentors and the rest of the team. Don't hesitate to join the IRC channels and ask questions: keep in mind that there are no stupid questions! | We don't expect you to produce a perfect application without any help at all. We strongly encourage you to discuss your plans and your application with us while you're preparing it, to ensure your ideas align well with our own thoughts on the tasks, and that your objectives are achievable. It is also the perfect chance to already get to know your potential mentors and the rest of the team. Don't hesitate to join the IRC channels and ask questions: keep in mind that there are no stupid questions! | ||
| Line 20: | Line 20: | ||
: A good project will not just be fun to work on, but also generally useful to others. Why do you think it's a good project for us? | : A good project will not just be fun to work on, but also generally useful to others. Why do you think it's a good project for us? | ||
* ''Deliverables'' | * ''Deliverables'' | ||
: The deliverables will be used to evaluate your progress/success at the | : The deliverables will be used to evaluate your progress/success at the intermediate/final evaluations, so it's very important that you list some clear goals here. Some examples: | ||
:* "Get scene X in game Y working." | :* "Get scene X in game Y working." | ||
:* "Improve feature X in ways Y and Z." | :* "Improve feature X in ways Y and Z." | ||
| Line 28: | Line 28: | ||
: Finally, be sure to describe some '''milestones''', your high-level targets for the project. A milestone should be connected to the progress/accomplishment of goals. You should, at the very least, define 2 (two) milestones here. Again, describe the milestones and elaborate on your reasons for defining exactly these milestones. When you plan to accomplish the milestones will be handled in the schedule and not here. | : Finally, be sure to describe some '''milestones''', your high-level targets for the project. A milestone should be connected to the progress/accomplishment of goals. You should, at the very least, define 2 (two) milestones here. Again, describe the milestones and elaborate on your reasons for defining exactly these milestones. When you plan to accomplish the milestones will be handled in the schedule and not here. | ||
* ''Project Schedule'' | * ''Project Schedule'' | ||
: Your summer work on your project will last for 12 weeks. Create a proposed schedule with a granularity of weeks. This schedule should (among other things) explain how long each of your goals is planned to take, and you should connect the weeks to the Summer of Code schedule, i.e. clearly make the start, | : Your summer work on your project will last for 12 weeks. Create a proposed schedule with a granularity of weeks. This schedule should (among other things) explain how long each of your goals is planned to take, and you should connect the weeks to the Summer of Code schedule, i.e. clearly make the start, intermediate evaluations, etc. visible. | ||
: Obviously we want to see a connection between your goals and your schedule: try to elaborate why you think X takes time Y and what possible issues might arise here. Your schedule will probably change once you've started working on your project, so we want to know what kind of risks and problems you think might cause such changes. | : Obviously we want to see a connection between your goals and your schedule: try to elaborate why you think X takes time Y and what possible issues might arise here. Your schedule will probably change once you've started working on your project, so we want to know what kind of risks and problems you think might cause such changes. | ||
: Last but not least, put a fixed date for each milestone you defined here. We want at least one milestone before the mid-term. | : Last but not least, put a fixed date for each milestone you defined here. We want at least one milestone before the mid-term. | ||