aboutsummaryrefslogtreecommitdiff
path: root/community/gsoc/student_application_form.mdwn
Commit message (Collapse)AuthorAgeFilesLines
* Fix typos and spelling on GSoC pagesCarl Fredrik Hammar2010-03-101-6/+6
|
* gsoc/student_application_form: add question for introductionantrik2010-03-101-0/+4
|
* gsoc/student_application_form: add question about contact informationantrik2010-03-101-0/+4
|
* gsoc/student_application_form: wording and punctuation fixes/improvementsantrik2010-03-101-16/+19
|
* gsoc/student_application_form: be slightly more explicit about time constraintsantrik2010-03-101-2/+2
| | | | | Hopefully this will make it somewhat clearer that we are serious about this, but without sounding too accusatory...
* gsoc/student_application_form: more emphasis on additional requirements ↵antrik2010-03-101-1/+2
| | | | being mandatory
* Simplify some links.Thomas Schwinge2009-05-181-2/+2
|
* Prefix directives.Thomas Schwinge2009-05-181-2/+2
|
* GSoC student application form: Add note on application titleantrik2009-03-121-0/+9
|
* Update copyright years.Thomas Schwinge2009-03-051-1/+1
|
* Add hook for additional information in GSoC student application formantrik2009-03-051-0/+2
|
* Add question about code maintainance after GSoC end to student application formantrik2009-03-051-0/+3
| | | | | The main purpose is to get a clear statement about whether the student intends to stick around after the end of GSoC...
* Explain question about possible obstacles in GSoC student application formantrik2009-03-051-0/+4
|
* Explain question about time commitment in GSoC student application formantrik2009-03-051-0/+4
|
* Split time commitment and other activities questions in GSoC student ↵antrik2009-03-051-4/+6
| | | | | | | | 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.
* Reworked and explained vacations/exams question in GSoC student application formantrik2009-03-051-1/+6
|
* Merged and reworked IRC and time zone questions in GSoC student application formantrik2009-03-051-6/+9
|
* Reworked mailing list question in GSoC student application formantrik2009-03-051-2/+6
| | | | | | | | 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.
* Explain questions about Hurd in GSoC student application formantrik2009-03-051-0/+5
|
* Merge questions about Hurd project in GSoC student application formantrik2009-03-051-3/+2
|
* Drop questions about Hurd experience from GSoC student application formantrik2009-03-051-7/+0
| | | | | | | 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.
* Drop question about how free software projects work from GSoC student ↵antrik2009-03-051-5/+0
| | | | | | | | 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.
* Punctuation fix in GSoC student application formantrik2009-03-051-1/+1
|
* Merge questions about Hurd involvement and free software involvment in GSoC ↵antrik2009-03-051-3/+2
| | | | student application form
* Explain question about learning in GSoC student application formantrik2009-03-051-0/+5
|
* State some expectations regarding the schedule in GSoC student application formantrik2009-03-051-0/+13
|
* Minor rewording is GSoC student application formantrik2009-03-051-1/+1
|
* Replaced introduction section of GSoC student application formantrik2009-03-051-16/+83
| | | | | | | | | | | | | | | 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...
* Drop note about size limit of GSoC student application formantrik2009-03-051-5/+0
| | | | | 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.
* Use normal wiki link for [[IRC]]antrik2008-03-191-4/+3
|
* Rephrased note on 7500 character limit, and linked to FAQantrik2008-03-191-1/+4
|
* web commit by http://arnebab.livejournal.com/GNU Hurd wiki engine2008-03-171-0/+2
|
* Corrected language and other minor improvementsantrik2008-03-121-4/+4
|
* Link to contact pagesantrik2008-03-121-3/+4
|
* Added another question, about compiling Hurdantrik2008-03-121-0/+4
|
* web commit by antrik: Added questions "what makes you interested in the ↵GNU Hurd wiki engine2008-03-091-0/+6
| | | | Hurd" and "why did you choose this task"
* web commit by antrik: First draft for the student application formGNU Hurd wiki engine2008-03-091-0/+77