It’s been two weeks since i last posted my report on Darkserver. I could not post week two update as I had been down with bad health(seasonal changes + Loo). With the week coming to an end and /me recovering from fever, i badly hurt my right wrist and that was end of it. I somehow manage to move myself to a new city, Bengaluru. The week passed as a trauma for me :’( ...
Today, I got my GSoC welcome Kit. YaY!
The ‘Google Summer of Code’ code period began on June 17 and it’s already one week into it. Prior to the beginning of the coding period, I went into the depths of the darkserver codebase. In the current version of Darkserver, the link present in the libimporter are hardlinks and it is pretty well visible on Github So, I removed the urls and the values from the libimporter and made it configurable via config files. The config files are currently present in the configs/ directory. This will eventually help to allow us to add different job queues for different secondary architectures. ...
It was worth trying to sit down with pen and paper and sketch out the compete workflow of Darkserver. I got the idea to try out this stuff from Vivek’s blogpost. Though, I could not get hold of a board but A4 did the job for me and it is really proving out to be helpful. .. slides: ../galleries/random_scribblings.JPG ../galleries/random_scribblings2.JPG
The Google Summer of Code 2013 results was declared on 27th May 2013, in between my semester exam so i had no time to devote until the end of my semester exams and /me returning back to my home. With the beginning of the 2nd week of June, I started to hack around with the project, Darkserver. The project is available on GitHub. That week was pretty much a reading week rather than coding week as I had to go through all kinds of documentation. Darkserver is implemented using retask, which uses Redis. Though, I earlier little knowledge about the topics, I went thoroughly through the Redis documentation and googled more about Redis. ...