KDE @ Google Code-In
Google Code-In sounded really astounding, when I first got to know about it. But I was not really sure, if I was capable enough. Coding is just my passion that I developed 3 years ago (in 7th class) when they started teaching Visual Basic at school. But it is not necessary that you are good at your passion.
Still, when I checked out GCI's page, these words came popping out from the monitor - Open-Source, KDE, Linux, Fedora; and I felt like it is the opportunity I always wanted. I got introduced to Linux almost a year ago, and I loved the idea of Open Source. I dumped my old OS, and got deep into Kubuntu, and then quite recently switched to Fedora with KDE.
KDE-telepathyI took-off with GCI, and the second task (first with KDE) was for going through KDE-telepathy (chat client)'s pre release test procedure. I was a KDE user for a while, and used KTp to IM many times. But the real challenge in this task that I saw was that you had to compile KTp from source, cloning it's git repositories. I had worked with git but, Compiling software?? The only program(s) I ever compiled in my life were silly and short .cpp/.c files. Compiling something too big (relative to the helloworld.cpp) was a great adventure! Using cmake to compile all the components of KTp, meeting all the dependencies and all of the dependencies, and the dependd... oh. The first compile went fine but the account-settings component gave an error, that I discussed with my mentor on irc, and after some suggestions, and help, it started working perfectly!
The error message that I got had an error (Aye! the error had an error), Just the word 'telepathy' was to be replaced by 'ktp', it was noted by the mentor and he corrected and committed it on git in minutes. Here is the diff of the file http://goo.gl/N7Avv, and I am happy that Google Code-In made me contribute in the Foss world (even though it was such a small contribution).
The test procedure went nice, I reported the few errors in a .odt file, and the task was closed.
I Learnt: Testing, Compiling, IRC etiquettes etc.
AmarokAmarok, the best music player I have met yet. The moment I saw the task about testing amarok from git (yeah quite similar to the previous), I hit claim. I got to know about the build-dep tool that all major Linux package managers have, used to meet the dependencies needed to build a package, it really helped in compiling. Testing went superb! I got to know so many new features of Amarok, that I previously was unaware of. Getting guitar tabs of songs through Amarok is the best. I documented the testing I did, and task closed.
I Learnt: Features in Amarok, build-dep, Documenting reports formally etc.
Overall, the experience with KDE and GCI till now was very beautiful. I got to learn about the Free and Open Source world, and many topics about open source that were cloudy in my mind, are now clear. I discovered what really happens behind the scene, the making of my most used free softwares. PS: don't forget the best thing about this program is the exposure and the experience (and of course the prizes) ;)