65
edits
Difference between revisions of "Summer of Code/Project Rules"
Jump to navigation
Jump to search
mention that patches could also extend existing functionality
(some grammar corrections) |
(mention that patches could also extend existing functionality) |
||
| 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 their 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 their 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 | * Students are expected to submit a patch which fixes some known bug, extends functionality in some way, or is a start of their work which they are 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 has to be always at least ''compilable''. | * The code has to be always at least ''compilable''. | ||
* Commit often, commit early. | * Commit often, commit early. | ||