summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-02-25 08:35:27 +0100
committerantrik <antrik@users.sf.net>2009-02-25 08:35:27 +0100
commita7351814af53ef280fda8b84e45c0179e5195c4b (patch)
tree9a70b62c51049ad30b5167e421b2cf5f4aab85cc /community
parente34a7c5b111a6432d4c014f57dca75cb68a24254 (diff)
GSoC application: Higher expectations regarding student communication
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/organization_application.mdwn28
1 files changed, 17 insertions, 11 deletions
diff --git a/community/gsoc/organization_application.mdwn b/community/gsoc/organization_application.mdwn
index 711f55e5..be6867bb 100644
--- a/community/gsoc/organization_application.mdwn
+++ b/community/gsoc/organization_application.mdwn
@@ -198,17 +198,23 @@ should go smoothly.
* What steps will you take to encourage students to interact with your
project's community before, during and after the program?
-As part of the application process, we will ask students to answer very
-specific questions about our organisation and the project they chose, which
-they won't be able to answer without contacting us and discussing details
-already during the application phase. This way we make sure we only get
-studends able and willing to communicate with us.
-
-During the program, we will be asking the students actively about the work they
-do, problems they face, decisions they take etc.
-
-After the program we will continue discussing the projects, and ask the
-students to take part in these discussions.
+We try to make it very clear that we expect the students to get into regular
+contact with us before the end of the student selection process, and won't
+consider their applications otherwise. This way we know that the students are
+able and willing to communicate with us in the first place.
+
+After the selection, the regular contact will be kept up: We require the
+students to participate in weekly IRC meetings, where we ask the students
+actively about the work they do, problems they face, decisions they take etc.
+Furthermore, we will ask them to hang around on IRC most of the time while
+working on their projects, so we keep in close contact.
+
+We also require the students to join our main development mailing list, so any
+design questions etc. can be discussed there. We will encourage them to take
+part in other conversations, not directly related to their projects, as well.
+
+After the program we continue the regular meetings, still discussing the
+projects: The application of the code created, future directions etc.
* What will you do to ensure that your accepted students stick with the project
after GSoC concludes?