summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2009-03-10Drop kernel instrumentation (dtrace) GSoC taskantrik
The stuff Andrei worked on last year isn't quite ready yet, but leave it for now...
2009-03-10Server overriding GSoC task: Update "last year"...antrik
2009-03-10Server overriding GSoC task: Socket server overriding patch as exampleantrik
Mention Zheng Da's socket overriding patch as an example of approach (1), intead of mentioning it in the "status" section.
2009-03-10Server overriding GSoC task: Explicitely mention relation to virtualization taskantrik
2009-03-10Glue code GSoC task: Rework exercise suggestionantrik
2009-03-10Glue code GSoC task: Reword statement about previous experienceantrik
2009-03-10Glue code GSoC task: More explicitely suggest using ddekitantrik
2009-03-10Drop procfs GSoC taskantrik
While the procfs produced in last year's GSoC is still very buggy, this probably doesn't justify another GSoC project.
2009-03-10File locking GSoC task: Update exercise suggestionantrik
While the suggestion is certainly good as an exercise, it is probably not suitable for producing an actual patch quickly. Warn about this, and explicitely mention that finding a different task might be necessary.
2009-03-10Drop namespace-based translator selection GSoC taskantrik
Sergiu Ivanov is working on this.
2009-03-10Virtualization GSoC task: Drop subhurds subtaskantrik
Zheng Da is currently working on rootless subhurds etc.
2009-03-10Language bindings GSoC task: Rewrote note on previous Perl workantrik
Explicitely mention that the previous work can serve as a reference only -- most likely we can't use it directly because of missing copyright assignment. Probably it also uses a suboptimal technical approach. (Haven't checked.)
2009-03-10Language bindings GSoC task: Better starting point for Python bindingsantrik
2009-03-10Partial revert: Too much deleted while updating Lisp statusantrik
2009-03-09Mention cthread vs. pthread problem in language bindings GSoC taskantrik
2009-03-09Language bindings GSoC task: Lisp implemented last yearantrik
2009-03-09GSoC project ideas list: Inline each subpage individuallyantrik
This gives us better control -- in particular over the ordering. It will also allow easily disabling ideas without removing them alltogether, which I consider useful.
2009-03-09put myself as possible mentor, add comment on the pthread projectSamuel Thibault
2009-03-08Use actual URL instead of wiki link for project list in GSoC application formantrik
This way it can be pasted into the application form directly.
2009-03-07Update questions in GSoC application according to the actual formantrik
2009-03-07Rework introduction section in GSoC project ideas listantrik
Make it clear that we explicitely require the students to contact us, and to submit a patch as part of the application process. Most of this information is redundant with the introduction section of the student application form. This is not a problem: If they read it twice, there is a better chance that they will take it seriously...
2009-03-06Remove junk file.Thomas Schwinge
2009-03-05(no commit message)Thom
2009-03-05community/gsoc/project_ideas: Split into subpages.Thomas Schwinge
2009-03-05Use the git CLI syntax one is supposed to use these days.Thomas Schwinge
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.
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