summaryrefslogtreecommitdiff
path: root/community/gsoc
AgeCommit message (Collapse)Author
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-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-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
2008-11-23Move user pages where they belong.Thomas Schwinge
2008-11-23Move GSoC 2008 IRC meetings minutes pages.Thomas Schwinge
2008-11-19Revert "microkernel/mach/gnumach -> microkernel/mach/gnu_mach"Thomas Schwinge
This reverts commit ae9e4e22a7ce8b2b56e98ff1708c2e8d42eefd69. I've changed my mind again. Also resolve conflicts and adapt all new uses of the path.
2008-11-05microkernel/mach/gnumach -> microkernel/mach/gnu_machThomas Schwinge
2008-10-08UNIX.Thomas Schwinge
2008-09-11Added some text markup to gsoc and gsoc project ideas.arnebab
2008-09-10Major status update for end of GSoCantrik
2008-04-25Add status notes to selected projectsantrik
2008-04-07Link to application formantrik
2008-04-07Add exercise for diskfs locking tooantrik
2008-04-07Add exercises to all project ideasantrik
2008-04-05List possible mentors for (some) projectsantrik
2008-04-03Use correct syntax for external links.Thomas Schwinge
2008-04-02(glue code) Suggest ddekit as alternativeantrik
2008-04-02Remove note about ``Xen's high-level driver interface'', as this is what the ↵Thomas Schwinge
Xen port of GNU Mach is providing already.
2008-04-01(VM tuning) Add linkantrik
2008-03-31Add warning about procfs task popularityantrik
2008-03-31(procfs) Readded list of examples for tools using procfsantrik
2008-03-30Simplify hyperlinks.Thomas Schwinge
2008-03-30Added links for server overriding discussionsantrik
2008-03-30Described Lisp part of the binding project and proposed mentorship for it.Pierre THIERRY
2008-03-30community/gsoc/libchannel -> hurd/libchannelThomas Schwinge
2008-03-29community/gsoc/procfs/* -> hurd/translator/procfs/*Thomas Schwinge
2008-03-29community/gsoc/community/gsoc/procfs/htop: Remove duplicate and misplaced page.Thomas Schwinge
2008-03-29community/gsoc/community/gsoc/procfs/procps: Remove empty page.Thomas Schwinge
2008-03-29community/gsoc/hurd/libtrivfs: Remove empty page.Thomas Schwinge
2008-03-29web commit by vincentvikram: Removed initial commentsGNU Hurd wiki engine
2008-03-29web commit by http://madhusudancs.myvidoop.com/GNU Hurd wiki engine
2008-03-28web commit by flaviocruzGNU Hurd wiki engine
2008-03-28web commit by flaviocruzGNU Hurd wiki engine