Difference between revisions of "Summer of Code/Project Rules"

Jump to navigation Jump to search
Line 16: Line 16:
* ... we require you to '''communicate with your mentor''' every second day. If you fail to do that for longer than three days without arrangement, you will fail the program.
* ... we require you to '''communicate with your mentor''' every second day. If you fail to do that for longer than three days without arrangement, you will fail the program.
** ''Communication is key to a successful GSoC project and experience has shown that students that do not check in with their mentors (and the wider community) tend to struggle and produce weaker outputs.''
** ''Communication is key to a successful GSoC project and experience has shown that students that do not check in with their mentors (and the wider community) tend to struggle and produce weaker outputs.''
* ... we ask you to '''keep a weblog''' (BLOG) with posts on a weekly or more frequent basis detailing their progress and experiences with their project/GSoC.  
* ... we ask you to '''keep a weblog''' (BLOG) with posts on a weekly or more frequent basis detailing your progress and experiences with your project/GSoC.  
** ''This provides a valuable avenue for feedback and helps involvement of the wider community. It also helps you to sort your thoughts and determine your own progress. Note that the blogs will be aggregated onto [http://planet.scummvm.org/ ScummVM's Planet site] so language and tone should be set accordingly.''
** ''This provides a valuable avenue for feedback and helps involvement of the wider community. It also helps you to sort your thoughts and determine your own progress. Note that the blogs will be aggregated onto [http://planet.scummvm.org/ ScummVM's Planet site] so language and tone should be set accordingly.''
* ... your code must comply to our '''[[Code Formatting Conventions]]'''.
* ... your code must comply to our '''[[Code Formatting Conventions]]'''.
208

edits

Navigation menu