cadey
/
nim-wiki
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Improve phrasing

This commit is contained in:
Flaviu Tamas 2015-02-19 21:59:25 -05:00
parent d9091b1b76
commit 24c07252c0
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
GSoC-2015-Organization-Application.rest
View File

@ -35,10 +35,10 @@ 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?
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 or core contributor could jump in as a last resort.
Our mentors are core members of the community, including Andreas Rumpf, the author of the Nim programming language. As all mentors are heavily invested into Nim, it is highly doubtful that anyone would disappear. Upon the disappearance of a mentor, another mentor or core contributor could replace them.
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 beforehand. During the program we also expect the students to continuously interact with us via IRC.
We're asking students to join our IRC channel and discuss potential ideas with us. It's very important for us to get in touch with students before in order to find a fitting project for each student and help with their independent research beforehand. During the program we also expect the students to continuously interact with us via IRC.
What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes?
Firstly we will make sure that students enjoy their GSoC with Nim, by being patient with students and at the same time giving them the opportunity to show their true talents. At the end of the summer we will propose ideas of further improving their GSoC work and other potential projects with Nim.