Talk:Summer of Code/Application/2007

I would suggest a different approach for the "When things go wrong" section. Instead of claiming that we already know all ways in which this can occur (which likely is wrong anyway), we could approach it more like this: "We will use a proactive approach, where we first try to minimize the risk of contact breakdown by doing XYZ. In case it happens anyway, we will make sure to exchange as many contact information as possible, like phone numbers. BLA BLA. In the worst case, we will have to add a negative part to the report (and we will make sure the students are aware of all this)." I am at work right now, but I'll try to write an alternate proposal for this section tonight if time permits. Fingolfin 10:23, 6 March 2007 (UTC)

Quite right. Actually re-reading it today I find that piece of text horrible! It certainly needs rework - what you suggest is in the right direction. My original bulletted stuff looks decent, don't know why this ended up like this :-) Jubanka 11:04, 6 March 2007 (UTC)

looks better and better! thanks for your hard work Max! Jubanka 20:29, 7 March 2007 (UTC)

"A common cause (we believe, based on our own experiences as students *g*) is a lack of structure in the assigned work, this manifests itself as 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 monitor the progress with the students and discuss it with them regularly (at least weekly). We hope to detect potential problems early on this way, thus being able to help the students get around them. This should help to maximise the productivity of all involved."

Not sure that that slight rewording above is much better but there is something about the original paragraph that seems odd to me. I can't quite put my finger on it. - Anyway, I will carry on reading through and pop any other suggestions on this page DJWillis 11:01, 8 March 2007 (UTC)