summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2010-03-10 06:33:47 +0100
committerantrik <antrik@users.sf.net>2010-03-10 06:33:47 +0100
commit899869fd2ebf41654fd149641e10c3c88468c544 (patch)
tree2ff9d577096e1a6f8736566369ef17998877dc2f /community
parent16f30908a3f67573bee3648bc4220d47b80234b5 (diff)
gsoc/student_application_form: be slightly more explicit about time constraints
Hopefully this will make it somewhat clearer that we are serious about this, but without sounding too accusatory...
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/student_application_form.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/student_application_form.mdwn b/community/gsoc/student_application_form.mdwn
index 954507d5..3f696ca4 100644
--- a/community/gsoc/student_application_form.mdwn
+++ b/community/gsoc/student_application_form.mdwn
@@ -191,8 +191,8 @@ intend to make sure you will be able to dedicate sufficient time to your
project nevertheless?
Please be open about this, and also mention things you are not yet sure about.
-We can be flexible about time arrangements; but we need to know about any
-possible obstacles up front.
+We can be flexible about time arrangements; but we absolutely need to know about any
+possible obstacles up front. Surprises on that score are not acceptable.
* How do you intend to make sure that your code will keep on being maintained
and supported properly after the end of the GSoC program?