Difference between revisions of "Summer of Code/Project Rules"
Jump to navigation
Jump to search
(Put together some project rules) |
(Add infor about code application) |
||
| Line 4: | Line 4: | ||
* We demand a comprehensive and detailed plan for all 12 weeks of your project. Include risk mitigation. | * We demand a comprehensive and detailed plan for all 12 weeks of your project. Include risk mitigation. | ||
* We require each student to communicate with mentor every second day. If you fail to do that for longer than 3 days, you will fail the program. | * We require each student to communicate with mentor every second day. If you fail to do that for longer than 3 days, you will fail the program. | ||
* Students are expected to submit a patch which fixes some known bug or be start of their work which they applying for. | |||
* Students have to blog about their progress on a weekly basis or more often. | * Students have to blog about their progress on a weekly basis or more often. | ||
* Stick to our [[Code Formatting Conventions]]. | * Stick to our [[Code Formatting Conventions]]. | ||
* The code have to be always at least ''compilable''. | * The code have to be always at least ''compilable''. | ||
* Commit often, commit early. | * Commit often, commit early. | ||
Revision as of 21:50, 9 March 2009
Here you will find several important rules which you have to conform in order to be eligible to application as a student for ScummVM project.
- Google Summer of Code is a full time job. If you consider getting additional part time job or have exams, do not apply.
- We demand a comprehensive and detailed plan for all 12 weeks of your project. Include risk mitigation.
- We require each student to communicate with mentor every second day. If you fail to do that for longer than 3 days, you will fail the program.
- Students are expected to submit a patch which fixes some known bug or be start of their work which they applying for.
- Students have to blog about their progress on a weekly basis or more often.
- Stick to our Code Formatting Conventions.
- The code have to be always at least compilable.
- Commit often, commit early.