From ee41f513a7f9e23d8fe5b62e7d0feba69af06cb1 Mon Sep 17 00:00:00 2001 From: Dennis Felsing Date: Sun, 15 Feb 2015 01:15:41 +0100 Subject: [PATCH] Updated GSoC 2015 Organization Application (rest) --- GSoC-2015-Organization-Application.rest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/GSoC-2015-Organization-Application.rest b/GSoC-2015-Organization-Application.rest index bd3656e..7ca4d8c 100644 --- a/GSoC-2015-Organization-Application.rest +++ b/GSoC-2015-Organization-Application.rest @@ -35,7 +35,7 @@ What is your plan for dealing with disappearing students? By regularly interacting with the student and getting feedback from both sides, problems can be avoided early. I believe this will significantly reduce the risk of a student disappearing. What is your plan for dealing with disappearing mentors? - I highly doubt it, but another mentor could jump in. Especially Andreas Rumpf, the author of the Nim programming language, will not just disappear. + Our mentors are core members of the community, including Andreas Rumpf, the author of the Nim programming language himself. I highly doubt that any mentor would disappear since we don't take this responsibility lightly, but another mentor could jump in. What steps will you take to encourage students to interact with your project's community before and during the program? On our ideas page we're asking them to join our IRC channel and discuss potential ideas with us. It's very important for us to get in touch with students before, to make sure to find a fitting project for each student, and make them understand and help with their independent research.