| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Diskfs locking GSoC task: Change exercise | antrik | 2009-03-12 | 1 | -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 review | antrik | 2009-03-12 | 1 | -0/+4 | |
| | | ||||||
| * | NFS GSoC task: Update exercise suggestion | antrik | 2009-03-12 | 1 | -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 discussion | antrik | 2009-03-12 | 1 | -0/+6 | |
| | | ||||||
| * | NFS GSoC task: Mention that locking is problematic in general | antrik | 2009-03-12 | 1 | -0/+3 | |
| | | ||||||
| * | (no commit message) | tokijici | 2009-03-11 | 1 | -0/+23 | |
| | | ||||||
| * | Network stack GSoC task: Additional exercise suggestion | antrik | 2009-03-10 | 1 | -2/+4 | |
| | | ||||||
| * | Network stack GSoC task: Monolitic implementation sufficient for the beginnig | antrik | 2009-03-10 | 1 | -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 sentence | antrik | 2009-03-10 | 1 | -1/+1 | |
| | | ||||||
| * | Drop kernel instrumentation (dtrace) GSoC task | antrik | 2009-03-10 | 1 | -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"... | antrik | 2009-03-10 | 1 | -1/+1 | |
| | | ||||||
| * | Server overriding GSoC task: Socket server overriding patch as example | antrik | 2009-03-10 | 1 | -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 task | antrik | 2009-03-10 | 1 | -1/+2 | |
| | | ||||||
| * | Glue code GSoC task: Rework exercise suggestion | antrik | 2009-03-10 | 1 | -3/+5 | |
| | | ||||||
| * | Glue code GSoC task: Reword statement about previous experience | antrik | 2009-03-10 | 1 | -3/+3 | |
| | | ||||||
| * | Glue code GSoC task: More explicitely suggest using ddekit | antrik | 2009-03-10 | 1 | -2/+5 | |
| | | ||||||
| * | Drop procfs GSoC task | antrik | 2009-03-10 | 1 | -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 suggestion | antrik | 2009-03-10 | 1 | -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 task | antrik | 2009-03-10 | 1 | -1/+0 | |
| | | | | | Sergiu Ivanov is working on this. | |||||
| * | Virtualization GSoC task: Drop subhurds subtask | antrik | 2009-03-10 | 1 | -7/+1 | |
| | | | | | Zheng Da is currently working on rootless subhurds etc. | |||||
| * | Language bindings GSoC task: Rewrote note on previous Perl work | antrik | 2009-03-10 | 1 | -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 bindings | antrik | 2009-03-10 | 1 | -4/+6 | |
| | | ||||||
| * | Partial revert: Too much deleted while updating Lisp status | antrik | 2009-03-10 | 1 | -0/+11 | |
| | | ||||||
| * | Mention cthread vs. pthread problem in language bindings GSoC task | antrik | 2009-03-09 | 1 | -0/+11 | |
| | | ||||||
| * | Language bindings GSoC task: Lisp implemented last year | antrik | 2009-03-09 | 1 | -42/+3 | |
| | | ||||||
| * | GSoC project ideas list: Inline each subpage individually | antrik | 2009-03-09 | 1 | -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 project | Samuel Thibault | 2009-03-09 | 3 | -2/+5 | |
| | | ||||||
| * | Use actual URL instead of wiki link for project list in GSoC application form | antrik | 2009-03-08 | 1 | -1/+1 | |
| | | | | | This way it can be pasted into the application form directly. | |||||
| * | Update questions in GSoC application according to the actual form | antrik | 2009-03-07 | 1 | -45/+44 | |
| | | ||||||
| * | Rework introduction section in GSoC project ideas list | antrik | 2009-03-07 | 1 | -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... | |||||
| * | Remove junk file. | Thomas Schwinge | 2009-03-06 | 1 | -23/+0 | |
| | | ||||||
| * | (no commit message) | Thom | 2009-03-05 | 1 | -0/+23 | |
| | | ||||||
| * | community/gsoc/project_ideas: Split into subpages. | Thomas Schwinge | 2009-03-05 | 25 | -978/+1176 | |
| | | ||||||
| * | Use the git CLI syntax one is supposed to use these days. | Thomas Schwinge | 2009-03-05 | 1 | -3/+4 | |
| | | ||||||
| * | Update copyright years. | Thomas Schwinge | 2009-03-05 | 2 | -2/+2 | |
| | | ||||||
| * | Add hook for additional information in GSoC student application form | antrik | 2009-03-05 | 1 | -0/+2 | |
| | | ||||||
| * | Add question about code maintainance after GSoC end to student application form | antrik | 2009-03-05 | 1 | -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 form | antrik | 2009-03-05 | 1 | -0/+4 | |
| | | ||||||
| * | Explain question about time commitment in GSoC student application form | antrik | 2009-03-05 | 1 | -0/+4 | |
| | | ||||||
| * | Split time commitment and other activities questions in GSoC student ↵ | antrik | 2009-03-05 | 1 | -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 form | antrik | 2009-03-05 | 1 | -1/+6 | |
| | | ||||||
| * | Merged and reworked IRC and time zone questions in GSoC student application form | antrik | 2009-03-05 | 1 | -6/+9 | |
| | | ||||||
| * | Reworked mailing list question in GSoC student application form | antrik | 2009-03-05 | 1 | -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 form | antrik | 2009-03-05 | 1 | -0/+5 | |
| | | ||||||
| * | Merge questions about Hurd project in GSoC student application form | antrik | 2009-03-05 | 1 | -3/+2 | |
| | | ||||||
| * | Drop questions about Hurd experience from GSoC student application form | antrik | 2009-03-05 | 1 | -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 ↵ | antrik | 2009-03-05 | 1 | -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 form | antrik | 2009-03-05 | 1 | -1/+1 | |
| | | ||||||
| * | Merge questions about Hurd involvement and free software involvment in GSoC ↵ | antrik | 2009-03-05 | 1 | -3/+2 | |
| | | | | | student application form | |||||
| * | Explain question about learning in GSoC student application form | antrik | 2009-03-05 | 1 | -0/+5 | |
| | | ||||||
 |
index : web.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| aboutsummaryrefslogtreecommitdiff |