State some expectations regarding the schedule in GSoC student application form

1 files changed, 13 insertions, 0 deletions

diff --git a/community/gsoc/student_application_form.mdwn b/community/gsoc/student_application_form.mdwn
index bab2fe1a..4394a6fe 100644
--- a/community/gsoc/student_application_form.mdwn
+++ b/community/gsoc/student_application_form.mdwn
@@ -102,6 +102,19 @@ if necessary. And don't hesitate to ask us if you have any doubts :-)
 only guesses; but try to be specific about all the individual steps you will
 have to do to complete the task.
 
+Note: By the end of the summer session, the code is expected to be in a state
+ready to be merged to mainline. Experience shows that adding the "final
+touches" necessary for that, tends to take up quite a lot of time -- there are
+always some bugs here and there, some misunderstandings about how things are
+supposed to work, build system issues, missing documentation, forgotten bits,
+and so on. Thus, the schedule should suppose that a larger part of the main
+implementation work will be done by midterm!
+
+Also note that by the beginning of the summer session, you need to be able to
+work on the task at more or less full speed -- meaning that you need to get
+familiar with the code, think through the design (and discuss it with us) etc.
+already in the interim period *before* the summer session.
+
 * What things will you have to learn to be able to complete the project? What
 do you already know?