summaryrefslogtreecommitdiff
path: root/community/gsoc/student_application_form.mdwn
AgeCommit message (Collapse)Author
2010-03-10Fix typos and spelling on GSoC pagesCarl Fredrik Hammar
2010-03-10gsoc/student_application_form: add question for introductionantrik
2010-03-10gsoc/student_application_form: add question about contact informationantrik
2010-03-10gsoc/student_application_form: wording and punctuation fixes/improvementsantrik
2010-03-10gsoc/student_application_form: be slightly more explicit about time constraintsantrik
Hopefully this will make it somewhat clearer that we are serious about this, but without sounding too accusatory...
2010-03-10gsoc/student_application_form: more emphasis on additional requirements ↵antrik
being mandatory
2009-05-18Simplify some links.Thomas Schwinge
2009-05-18Prefix directives.Thomas Schwinge
2009-03-12GSoC student application form: Add note on application titleantrik
2009-03-05Update copyright years.Thomas Schwinge
2009-03-05Add hook for additional information in GSoC student application formantrik
2009-03-05Add question about code maintainance after GSoC end to student application formantrik
The main purpose is to get a clear statement about whether the student intends to stick around after the end of GSoC...
2009-03-05Explain question about possible obstacles in GSoC student application formantrik
2009-03-05Explain question about time commitment in GSoC student application formantrik
2009-03-05Split time commitment and other activities questions in GSoC student ↵antrik
application form While these questions are related in establishing how much time the student will work on the project, they need to be handled (and explained) distinctly.
2009-03-05Reworked and explained vacations/exams question in GSoC student application formantrik
2009-03-05Merged and reworked IRC and time zone questions in GSoC student application formantrik
2009-03-05Reworked mailing list question in GSoC student application formantrik
Dropped bit about mailing list experience in general. It doesn't really mattter for our selection process. Also, make it explicit that this in not really a question, but rather a hint to subscribe ASAP.
2009-03-05Explain questions about Hurd in GSoC student application formantrik
2009-03-05Merge questions about Hurd project in GSoC student application formantrik
2009-03-05Drop questions about Hurd experience from GSoC student application formantrik
The purpose of these question was to encourage students to get some experience with using and developing Hurd during the application process. This indirect hint didn't really work anyways; and it's not necessary anymore, as we now explicitely require submitting a patch.
2009-03-05Drop question about how free software projects work from GSoC student ↵antrik
application form The students should have enough chance to get familiar with the process while creating/submitting a patch, required as part of the application process.
2009-03-05Punctuation fix in GSoC student application formantrik
2009-03-05Merge questions about Hurd involvement and free software involvment in GSoC ↵antrik
student application form
2009-03-05Explain question about learning in GSoC student application formantrik
2009-03-05State some expectations regarding the schedule in GSoC student application formantrik
2009-03-05Minor rewording is GSoC student application formantrik
2009-03-05Replaced introduction section of GSoC student application formantrik
Aside from rewording in general, we now explicitely demand that students contact us during the application period -- instead of just suggesting that they will really need to do so in order to properly answer the questions, and hoping that they take the hint... It is important that they contact us, and there is really no reason not to demand it explicitely. Also, introducing explicit patch requirement. (Instead of just asking for some "exercises" through the feedback form after they submit their applications...) Generally, we try to be much more clear about our expectations up front. This should make our work much easier when giving feedback for the applications. Also it should result in better applications -- and more happy students...
2009-03-05Drop note about size limit of GSoC student application formantrik
The FAQ for this year no longer explicitely mentions a limit -- although it still talks about external links... Let's assume there is no limit anymore.
2008-03-19Use normal wiki link for [[IRC]]antrik
2008-03-19Rephrased note on 7500 character limit, and linked to FAQantrik
2008-03-17web commit by http://arnebab.livejournal.com/GNU Hurd wiki engine
2008-03-12Corrected language and other minor improvementsantrik
2008-03-12Link to contact pagesantrik
2008-03-12Added another question, about compiling Hurdantrik
2008-03-09web commit by antrik: Added questions "what makes you interested in the ↵GNU Hurd wiki engine
Hurd" and "why did you choose this task"
2008-03-09web commit by antrik: First draft for the student application formGNU Hurd wiki engine