summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
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.
2009-03-04Remove junk file.Thomas Schwinge
2009-03-04(no commit message)mantha.s2000
2009-02-25GSoC application: Higher expectations regarding student communicationantrik
2009-02-24Don't have list of GSoC mentors for this year yet...antrik
2009-02-24Simplified answer to license question in GSoC applicationantrik
2009-02-24Describe 2008 GSoC participation in application formantrik
Also adapted question about no previous participation...
2009-02-24Mention getting long-term contributors as primary goal of GSoC participationantrik
This will probably make the Google folks happy, as this is officially the main purpose of the GSoC program... More importantly, past experience shows that even very skilled students are seldom able to leave a project in such a state that it is really useful for us without any followup work -- treating GSoC as a way to get code written by means of external sponsoring doesn't really work out. Finding long-term contributors is *much* more useful in the end.
2009-02-23Adapt questions in organization application according to list in 2009 FAQantrik
Note: Only the *questions* are adapted for now, not any answers...
2009-02-19Make it more obvious that these are not pure Hurd developer meetings.Thomas Schwinge
2009-02-17Correct links.Thomas Schwinge
2009-02-17hurd/ng/resource_management_problems -> ↵Thomas Schwinge
microkernel/mach/gnumach/open_issues/resource_management_problems
2009-02-17Move content of hurd/ng/history into hurd/history/port_to_l4.Thomas Schwinge
2009-02-17hurd/history/port_to_l4: Extend.Thomas Schwinge
2009-02-17hurd/faq/l4 -> hurd/history/port_to_l4Thomas Schwinge
2009-02-09Add two further links.Thomas Schwinge
2009-02-03We still have the regular IRC meetings, this is no longer GSoC 2008 specific.Thomas Schwinge
2009-02-03Move GSoC 2008 into its own page. Add note about GSoC 2009.Thomas Schwinge
2009-02-01Update.Thomas Schwinge
2009-01-27Update copyright year used for new pages.Thomas Schwinge
2009-01-27Remove bogus page.Thomas Schwinge
2009-01-27(no commit message)mukesh
2009-01-21Bring page.tmpl up to ikiwiki's 81b088866be5f55433c12e09c90e2ae404a8ed89.Thomas Schwinge
2009-01-19Move some pages, remove others that are either out of date or whose content ↵Thomas Schwinge
is duplicated somewhere else.
2009-01-13Remove some pages.Thomas Schwinge
2009-01-10MIG's dealloc and dealloc[] flags.Thomas Schwinge
2009-01-10Restructure.Thomas Schwinge
2009-01-09Enhance the colophon a bit.Thomas Schwinge
2009-01-09About page-in.Thomas Schwinge
2009-01-09Stub page for a devfs translator.Thomas Schwinge
2008-12-31correctionsarnuld
2008-12-28New homepagehttp://0xab.myopenid.com/
2008-12-17hurd/debugging/translator/capturing_stdout_and_stderr: Note about ↵Thomas Schwinge
line-buffering.
2008-12-16Remove bogus page.Thomas Schwinge
2008-12-16(no commit message)intijk