I've just sent my application. :) I'm looking forward for some feedback on it.
I like your application, it is quite detailed. My only comment doesn't need to be reflected in the text of application, it's more about our agreement how to interpret it.
For example, you reserve the whole week number 2 for the preparation of the toolchain. I understand that the purpose of reserving an entire week for this is to create some "buffer" for the unfortunate case that something goes wrong and that's OK that way.
But it is actually quite likely that preparing the toolchain will take much less time. If you happen to be ahead of the schedule at any time, it is advisable not to take a break and wait for the next planned week. You should go on with the next task immediately and keep the saved time as the buffer for safely completing the later milestones that might take longer than expected or even improving and extending the code already implemented (if the time is really of abundance).
I know that this advice might sound rather trivial, but we have had some unfortunate experience from GSoC when people took it rather too easy and despite having a lot of free time they delivered only a small contribution (that formally reflected their timeline, but not the money they expected to receive for it).
I'm looking forward for news about that. :)
Well, I have both good and bad news with respect to this. The security policy at ESA does not allow to grant access to the machines in the internal network to non-employees (to quite Maxime Perrotin, the organizer of SOCIS: "I have had this issue already in the past and hit a wall.").
However, there is still some hope, my other contact at ESA works with external contractors and there just might be some other way how to arrange it. We have to wait for the answer, it might time some time.
M.D. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
