Difference between revisions of "Summer of Code/Application/2007"

Summer of Code/Application/2007 (view source)

710 bytes added , 16:55, 7 March 2007

1,079

edits

@@ Line 68: / Line 68: @@
 As for the students, for starters we plan to exchange as much communication data as possible (cell phone numbers, postal addresses etc.). Through a friendly atmosphere we hope to minimize the risk of any student being "afraid" to report problems they might have etc.. On the other hand, we will make it clear that we expect dedicated work of the students and that unannounced/unjustified disappearances will draw consequences, like negative reports or even the failure of the whole project.
+A common cause (we believe, based on our own experiences as students *g*) is a lack of structure in the assigned work, resp. an inability of the student to make real progress. To avoid this, we will request that students come up with a (realistic) project plan / schedule. The mentors will watch the progress with the students and discuss it with them regularly (at least weekly). We hope to detect potential problems early this way, thus being able to help the students get around them, to the benefit of all. If that turns out to be impossible, we will have to deal with the consequences, just like with regular projects in a company. Projects *can* fail, after all, no matter how hard you try to avoid it.
 === Integrating students with the community ===