summaryrefslogtreecommitdiff
path: root/community
AgeCommit message (Collapse)Author
2009-03-12Package manager GSoC task: Change exercise suggestionantrik
The provious exercise was very nice and relevant, but probably too involved :-(
2009-03-12secure chroot GSoC task: Change exercise suggestionantrik
2009-03-12secure chroot GSoC task: Add links to ideas/discussionsantrik
2009-03-12secure chroot GSoC task: Fix typoantrik
2009-03-12Lexical .. GSoC task: Drop note on task being easyantrik
While this task certainly doesn't require much code to be written, I don't think it's actually easy for a newcomer...
2009-03-12tmpfs GSoC task: Update exerciseantrik
2009-03-12tmpfs GSoC task: Fix typosantrik
2009-03-12xmlfs GSoC task: Update exerciseantrik
Don't insist on the change being related to the existing xmlfs -- the skills required for doing minor changes on it aren't really any different from other translators.
2009-03-12xmlfs GSoC task: Stress requirement for good XML knowledgeantrik
2009-03-12xmlfs GSoC task: Mention XQueryantrik
2009-03-12Gnumach cleanup GSoC task: Reword exercise suggestionantrik
2009-03-12Gnumach cleanup GSoC task: Reworded section on things to doantrik
More explicitely state that the student should look at the code to find stuff to fix -- mention possible things only as examples.
2009-03-12mtab GSoC task: Changed exercise suggestionantrik
The previous suggestion would not produce a useful patch -- and it was probably too involved anyways...
2009-03-12GSoC student application form: Add note on application titleantrik
2009-03-12mtab GSoC task: fix typosantrik
2009-03-12I/O tuning GSoC task: Update exercise suggestionantrik
2009-03-12Pthreads conversion GSoC task: Update exercise suggestionantrik
2009-03-12Pthreads conversion GSoC task: Add Barry as possible mentorantrik
2009-03-12Pthreads conversion GSoC task: Merge notes about previous workantrik
Barry's work is available in the savannah task, so no need to mention it explicitely.
2009-03-12Pthreads conversion GSoC task: Drop cthreads wrapper optionantrik
As the native conversion is mostly done, such a wrapper probably wouldn't save any work now.
2009-03-12Pthread conversion GSoC task: Mention libfuse problemantrik
2009-03-12Diskfs locking GSoC task: Change exerciseantrik
The result of the previous exercise probably couldn't be considered a useful patch -- not suitable for going into mainline at least.
2009-03-12Diskfs locking GSoC task: Add note about code reviewantrik
2009-03-12NFS GSoC task: Update exercise suggestionantrik
Explicitely mention that the exercise might not be suitable for producing a patch, and it might be necessary to find an alternative task.
2009-03-12NFS GSoC task: Refer to Madhusudan's discussionantrik
2009-03-12NFS GSoC task: Mention that locking is problematic in generalantrik
2009-03-10Network stack GSoC task: Additional exercise suggestionantrik
2009-03-10Network stack GSoC task: Monolitic implementation sufficient for the beginnigantrik
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...
2009-03-10Network stack GSoC task: Fix sentenceantrik
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...