Open main menu

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

→‎During GSoC...: -- fixing "full time"
(s/IRC/Discord and other tweaks)
(→‎During GSoC...: -- fixing "full time")
Line 19: Line 19:
==During GSoC...==
==During GSoC...==
* We require you to '''communicate with your mentor''' every second day. '''Failing to do so for more than three days without arrangement will cause you to be dropped from the program.'''
* We require you to '''communicate with your mentor''' every second day. '''Failing to do so for more than three days without arrangement will cause you to be dropped from the program.'''
  ''Consider that GSoC is a full-time obligation. If you don't show up on a regular job for three days in a row, without any prior notice or reporting in as ill, you also run a high risk of being fired. Now, this is not exactly a regular day job and you don't have to come into an office every day. But communication is absolutely essential 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. In particular, if you feel you are behind your schedule or otherwise in troubles, talk to us as soon as possible. Do not hide from your mentor -- they are here to help you at all times. Finally, this obligation doesn't have to be a burden, but rather should be a fun opportunity to chat with a nice fellow coder about interesting topics.''
  ''Consider that GSoC is a nearly full-time obligation. If you don't show up on a regular job for three days in a row, without any prior notice or reporting in as ill, you also run a high risk of being fired. Now, this is not exactly a regular day job and you don't have to come into an office every day. But communication is absolutely essential 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. In particular, if you feel you are behind your schedule or otherwise in troubles, talk to us as soon as possible. Do not hide from your mentor -- they are here to help you at all times. Finally, this obligation doesn't have to be a burden, but rather should be a fun opportunity to chat with a nice fellow coder about interesting topics.''
* 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.  
* 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 the 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 the 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.''