GSoC Week 1: Getting to know you

It has been almost a week since hacking started, during the week my activities were focused in getting to know Darcs code, working in the skeleton of a high level document for the cache system, and looking at one of the warm-up issues, I won't say I already know how it all works, but I'm picking up new things each day and that's fine :).

From the Darcs code section, I know most of my work would be done in the module Darcs.Repository where the cache code lives, I still need to go deeply and see why, how, and what for is it used in each of the submodules, and how the cache system fits in all the system.

The first sketch of the skeleton for the high level document can be found in [1], we are putting all the administrative stuff in [4] to help us to keep track of everything.

About one of the first warm-up issues (1503), I found a possible way to fix it, you can read more about it in the last comment in [2], I haven't sent a patch yet, but I hope to have it before Tuesday.

While I was looking at this issue we noticed something weird in the log and we found another issue [3], I have a test left to do, and check if that is a problem specific to the installation in my server or is something from the current branch.

For the coming week I plan to:

- Close issue 1503.
- Pick up other issue.
- Elaborate more in the "Internal" section of the document.


[1]- http://wiki.darcs.net/DarcsInternals/CacheSystem
[2]- http://bugs.darcs.net/issue1503
[3]- http://bugs.darcs.net/issue1854
[4]- http://wiki.darcs.net/GoogleSummerOfCode/2010-Cache

Improving Darcs Performance - My GSoC Project.

I was accepted for this year GSoC, I will be working for Haskell.org and my project will be focus in improvements of Darcs performance, specifically I'll work in the global cache, you can find a full specification of my project here.

I'm pretty excited about it and really looking forward to start working on this, also my mentor would by Eric Kow (a.k.a kowey).

I'll try to keep weekly updates of how my work is going, and let you know about the ups and downs that I find in my way.

Thanks Haskell.org, thanks Darcs and last but not least thanks Google for given us this awesome opportunity.