| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2009-03-12 | Pthread conversion GSoC task: Mention libfuse problem | antrik | |
| 2009-03-12 | Diskfs locking GSoC task: Change exercise | antrik | |
| The result of the previous exercise probably couldn't be considered a useful patch -- not suitable for going into mainline at least. | |||
| 2009-03-12 | Diskfs locking GSoC task: Add note about code review | antrik | |
| 2009-03-12 | NFS GSoC task: Update exercise suggestion | antrik | |
| 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-12 | NFS GSoC task: Refer to Madhusudan's discussion | antrik | |
| 2009-03-12 | NFS GSoC task: Mention that locking is problematic in general | antrik | |
| 2009-03-10 | Network stack GSoC task: Additional exercise suggestion | antrik | |
| 2009-03-10 | Network stack GSoC task: Monolitic implementation sufficient for the beginnig | antrik | |
| 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-10 | Network stack GSoC task: Fix sentence | antrik | |
| 2009-03-10 | Drop kernel instrumentation (dtrace) GSoC task | antrik | |
| The stuff Andrei worked on last year isn't quite ready yet, but leave it for now... | |||
| 2009-03-10 | Server overriding GSoC task: Update "last year"... | antrik | |
| 2009-03-10 | Server overriding GSoC task: Socket server overriding patch as example | antrik | |
| Mention Zheng Da's socket overriding patch as an example of approach (1), intead of mentioning it in the "status" section. | |||
| 2009-03-10 | Server overriding GSoC task: Explicitely mention relation to virtualization task | antrik | |
| 2009-03-10 | Glue code GSoC task: Rework exercise suggestion | antrik | |
| 2009-03-10 | Glue code GSoC task: Reword statement about previous experience | antrik | |
| 2009-03-10 | Glue code GSoC task: More explicitely suggest using ddekit | antrik | |
| 2009-03-10 | Drop procfs GSoC task | antrik | |
| While the procfs produced in last year's GSoC is still very buggy, this probably doesn't justify another GSoC project. | |||
| 2009-03-10 | File locking GSoC task: Update exercise suggestion | antrik | |
| 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-10 | Drop namespace-based translator selection GSoC task | antrik | |
| Sergiu Ivanov is working on this. | |||
| 2009-03-10 | Virtualization GSoC task: Drop subhurds subtask | antrik | |
| Zheng Da is currently working on rootless subhurds etc. | |||
| 2009-03-10 | Language bindings GSoC task: Rewrote note on previous Perl work | antrik | |
| 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-10 | Language bindings GSoC task: Better starting point for Python bindings | antrik | |
| 2009-03-10 | Partial revert: Too much deleted while updating Lisp status | antrik | |
| 2009-03-09 | Mention cthread vs. pthread problem in language bindings GSoC task | antrik | |
| 2009-03-09 | Language bindings GSoC task: Lisp implemented last year | antrik | |
| 2009-03-09 | GSoC project ideas list: Inline each subpage individually | antrik | |
| 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-09 | put myself as possible mentor, add comment on the pthread project | Samuel Thibault | |
| 2009-03-08 | Use actual URL instead of wiki link for project list in GSoC application form | antrik | |
| This way it can be pasted into the application form directly. | |||
| 2009-03-07 | Update questions in GSoC application according to the actual form | antrik | |
| 2009-03-07 | Rework introduction section in GSoC project ideas list | antrik | |
| 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-05 | community/gsoc/project_ideas: Split into subpages. | Thomas Schwinge | |
| 2009-03-05 | Update copyright years. | Thomas Schwinge | |
| 2009-03-05 | Add hook for additional information in GSoC student application form | antrik | |
| 2009-03-05 | Add question about code maintainance after GSoC end to student application form | antrik | |
| The main purpose is to get a clear statement about whether the student intends to stick around after the end of GSoC... | |||
| 2009-03-05 | Explain question about possible obstacles in GSoC student application form | antrik | |
| 2009-03-05 | Explain question about time commitment in GSoC student application form | antrik | |
| 2009-03-05 | Split 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-05 | Reworked and explained vacations/exams question in GSoC student application form | antrik | |
| 2009-03-05 | Merged and reworked IRC and time zone questions in GSoC student application form | antrik | |
| 2009-03-05 | Reworked mailing list question in GSoC student application form | antrik | |
| 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-05 | Explain questions about Hurd in GSoC student application form | antrik | |
| 2009-03-05 | Merge questions about Hurd project in GSoC student application form | antrik | |
| 2009-03-05 | Drop questions about Hurd experience from GSoC student application form | antrik | |
| 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-05 | Drop 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-05 | Punctuation fix in GSoC student application form | antrik | |
| 2009-03-05 | Merge questions about Hurd involvement and free software involvment in GSoC ↵ | antrik | |
| student application form | |||
| 2009-03-05 | Explain question about learning in GSoC student application form | antrik | |
| 2009-03-05 | State some expectations regarding the schedule in GSoC student application form | antrik | |
| 2009-03-05 | Minor rewording is GSoC student application form | antrik | |
| 2009-03-05 | Replaced introduction section of GSoC student application form | antrik | |
| 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... | |||
 |
index : hurd-web.git | |
| Web pages |
| summaryrefslogtreecommitdiff |