aboutsummaryrefslogtreecommitdiff
path: root/community
Commit message (Collapse)AuthorAgeFilesLines
* Use proper file extension for Xorg GSoC ideas page [sigh]antrik2009-03-131-0/+0
|
* Added DRM porting to Xorg GSoC ideas listantrik2009-03-131-0/+39
| | | | | | This is not really a good project description, as it's not very specific about what work is actually required (I lack the knowledge for that) -- but I gues it doesn't hurt to offer it nevertheless...
* community/gsoc/project_ideas/apt_ftpfs: Initial version from IRC discussion.Thomas Schwinge2009-03-131-0/+64
| | | | Add missing file.
* community/gsoc/project_ideas/apt_ftpfs: Initial version from IRC discussion.Thomas Schwinge2009-03-131-0/+3
|
* Renamed xorg-ideas to xorg_ideasantrik2009-03-131-0/+0
|
* Add page with Hurd-specific GSoC tasks for Xorgantrik2009-03-131-0/+68
|
* GSoC ideas list: Additional hints regarding exercise task selectionantrik2009-03-121-2/+12
|
* Package manager GSoC task: Change exercise suggestionantrik2009-03-121-2/+3
| | | | | The provious exercise was very nice and relevant, but probably too involved :-(
* secure chroot GSoC task: Change exercise suggestionantrik2009-03-121-2/+5
|
* secure chroot GSoC task: Add links to ideas/discussionsantrik2009-03-121-0/+5
|
* secure chroot GSoC task: Fix typoantrik2009-03-121-1/+1
|
* Lexical .. GSoC task: Drop note on task being easyantrik2009-03-121-1/+1
| | | | | While this task certainly doesn't require much code to be written, I don't think it's actually easy for a newcomer...
* tmpfs GSoC task: Update exerciseantrik2009-03-121-3/+4
|
* tmpfs GSoC task: Fix typosantrik2009-03-121-2/+2
|
* xmlfs GSoC task: Update exerciseantrik2009-03-121-3/+4
| | | | | | 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.
* xmlfs GSoC task: Stress requirement for good XML knowledgeantrik2009-03-121-1/+1
|
* xmlfs GSoC task: Mention XQueryantrik2009-03-121-1/+1
|
* Gnumach cleanup GSoC task: Reword exercise suggestionantrik2009-03-121-2/+2
|
* Gnumach cleanup GSoC task: Reworded section on things to doantrik2009-03-121-3/+4
| | | | | More explicitely state that the student should look at the code to find stuff to fix -- mention possible things only as examples.
* mtab GSoC task: Changed exercise suggestionantrik2009-03-121-2/+3
| | | | | The previous suggestion would not produce a useful patch -- and it was probably too involved anyways...
* GSoC student application form: Add note on application titleantrik2009-03-121-0/+9
|
* mtab GSoC task: fix typosantrik2009-03-121-2/+2
|
* I/O tuning GSoC task: Update exercise suggestionantrik2009-03-121-2/+3
|
* Pthreads conversion GSoC task: Update exercise suggestionantrik2009-03-121-2/+4
|
* Pthreads conversion GSoC task: Add Barry as possible mentorantrik2009-03-121-1/+1
|
* Pthreads conversion GSoC task: Merge notes about previous workantrik2009-03-121-7/+2
| | | | | Barry's work is available in the savannah task, so no need to mention it explicitely.
* Pthreads conversion GSoC task: Drop cthreads wrapper optionantrik2009-03-121-7/+0
| | | | | As the native conversion is mostly done, such a wrapper probably wouldn't save any work now.
* Pthread conversion GSoC task: Mention libfuse problemantrik2009-03-121-0/+4
|
* Diskfs locking GSoC task: Change exerciseantrik2009-03-121-1/+4
| | | | | The result of the previous exercise probably couldn't be considered a useful patch -- not suitable for going into mainline at least.
* Diskfs locking GSoC task: Add note about code reviewantrik2009-03-121-0/+4
|
* NFS GSoC task: Update exercise suggestionantrik2009-03-121-3/+7
| | | | | Explicitely mention that the exercise might not be suitable for producing a patch, and it might be necessary to find an alternative task.
* 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
|