Changes

Jump to navigation Jump to search

Summer of Code/Project Rules

38 bytes added, 22:58, 9 March 2009
mention that patches could also extend existing functionality
* 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.
* Students are expected to submit a patch which fixes some known bug , extends functionality in some way, or be 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.
* Stick to our [[Code Formatting Conventions]].
* The code has to be always at least ''compilable''.
* Commit often, commit early.
65

edits

Navigation menu