summaryrefslogtreecommitdiff
path: root/community/gsoc
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-05 01:13:55 +0100
committerantrik <antrik@users.sf.net>2009-03-05 01:20:44 +0100
commitc4d1d9e92f5dc717d50a033ec2f19bfd2351ab4f (patch)
tree03a23528b70760526ffa7b49f194337514c392da /community/gsoc
parent657f1b0e0a19f74616ae374701dc35e6454ec3be (diff)
Add question about code maintainance after GSoC end to student application form
The main purpose is to get a clear statement about whether the student intends to stick around after the end of GSoC...
Diffstat (limited to 'community/gsoc')
-rw-r--r--community/gsoc/student_application_form.mdwn3
1 files changed, 3 insertions, 0 deletions
diff --git a/community/gsoc/student_application_form.mdwn b/community/gsoc/student_application_form.mdwn
index ee2f3745..12e985c9 100644
--- a/community/gsoc/student_application_form.mdwn
+++ b/community/gsoc/student_application_form.mdwn
@@ -183,3 +183,6 @@ 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.
+
+* 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?