aboutsummaryrefslogtreecommitdiff
path: root/community/gsoc
Commit message (Collapse)AuthorAgeFilesLines
...
* NFS GSoC task: Refer to Madhusudan's discussionantrik2009-03-121-0/+6
|
* NFS GSoC task: Mention that locking is problematic in generalantrik2009-03-121-0/+3
|
* Network stack GSoC task: Additional exercise suggestionantrik2009-03-101-2/+4
|
* Network stack GSoC task: Monolitic implementation sufficient for the beginnigantrik2009-03-101-4/+7
| | | | | | A modular implementation is not realistic in the GSoC timeframe; and starting with a monolithic one probably makes sense from an engineering standpoint anyways. Also, it's probably better than what we have now...
* Network stack GSoC task: Fix sentenceantrik2009-03-101-1/+1
|
* Drop kernel instrumentation (dtrace) GSoC taskantrik2009-03-101-1/+0
| | | | | The stuff Andrei worked on last year isn't quite ready yet, but leave it for now...
* Server overriding GSoC task: Update "last year"...antrik2009-03-101-1/+1
|
* Server overriding GSoC task: Socket server overriding patch as exampleantrik2009-03-101-5/+3
| | | | | Mention Zheng Da's socket overriding patch as an example of approach (1), intead of mentioning it in the "status" section.
* Server overriding GSoC task: Explicitely mention relation to virtualization taskantrik2009-03-101-1/+2
|
* Glue code GSoC task: Rework exercise suggestionantrik2009-03-101-3/+5
|
* Glue code GSoC task: Reword statement about previous experienceantrik2009-03-101-3/+3
|
* Glue code GSoC task: More explicitely suggest using ddekitantrik2009-03-101-2/+5
|
* Drop procfs GSoC taskantrik2009-03-101-1/+0
| | | | | While the procfs produced in last year's GSoC is still very buggy, this probably doesn't justify another GSoC project.
* File locking GSoC task: Update exercise suggestionantrik2009-03-101-2/+9
| | | | | | 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.
* Drop namespace-based translator selection GSoC taskantrik2009-03-101-1/+0
| | | | Sergiu Ivanov is working on this.
* Virtualization GSoC task: Drop subhurds subtaskantrik2009-03-101-7/+1
| | | | Zheng Da is currently working on rootless subhurds etc.
* Language bindings GSoC task: Rewrote note on previous Perl workantrik2009-03-101-2/+3
| | | | | | | 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.)
* Language bindings GSoC task: Better starting point for Python bindingsantrik2009-03-101-4/+6
|
* Partial revert: Too much deleted while updating Lisp statusantrik2009-03-101-0/+11
|
* Mention cthread vs. pthread problem in language bindings GSoC taskantrik2009-03-091-0/+11
|
* Language bindings GSoC task: Lisp implemented last yearantrik2009-03-091-42/+3
|
* GSoC project ideas list: Inline each subpage individuallyantrik2009-03-091-5/+24
| | | | | | | 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.
* put myself as possible mentor, add comment on the pthread projectSamuel Thibault2009-03-093-2/+5
|
* Use actual URL instead of wiki link for project list in GSoC application formantrik2009-03-081-1/+1
| | | | This way it can be pasted into the application form directly.
* Update questions in GSoC application according to the actual formantrik2009-03-071-45/+44
|
* Rework introduction section in GSoC project ideas listantrik2009-03-071-27/+54
| | | | | | | | | 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...
* community/gsoc/project_ideas: Split into subpages.Thomas Schwinge2009-03-0525-978/+1176
|
* Update copyright years.Thomas Schwinge2009-03-052-2/+2
|
* 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.
* GSoC application: Higher expectations regarding student communicationantrik2009-02-251-11/+17
|
* Don't have list of GSoC mentors for this year yet...antrik2009-02-241-3/+2
|
* Simplified answer to license question in GSoC applicationantrik2009-02-241-7/+1
|