It’s been a while since I posted something on this blog, partly due to my laziness, but also due to a chronic lack of time and patience to come home after an intellectually intense day of work and still have the peace of mind to gather my thoughts and put them in words. Today was, luckily, one of those days. Not because it was a particularly easy day at work (reengineering someone else’s code with little to non-existing documentation is never an easy job) but perhaps the intense gym session loosed my brains just enough for organized and coherent thought to just happen. In any case, I digress.
This post has three main themes. I will be talking about a platform for SOA applications called Turmeric (funny name, I know. I’m using for SOA the same I use in my lentil soup), open-source in general and finally, the Apache Software Foundation and some recent events I’ve been involved in.
True to the proverbial “feather in the cap”, I have been promoted to committer with the project I have been participating on during the last few months, Apache Derby. There’s not much to say except that it feels really good to have your hard work recognized
Apache Derby is a great project with a really nice community of helpful people and it was through Derby that I have participated and successfully completed the Google Summer of Code challenge for two years in a row! It’s always a great challenge even to the sharpest mind and most advanced skills because this is an extensive project that has already been around for more than a decade. Over this period different developers have participated on it which adds to the challenge of reengineering and simple engineering of new features when the need arises. I can’t say this is a disadvantage though as it is an excellent way of being exposed to actual production code from an IT giant (Apache Derby once was IBM Cloudscape). It’s also exciting because the changes that you make will actually have an impact on the thousands of people that use Apache Derby and for this reason all changes have to be done with most care to keep Derby’s performance up to the challenge as well as to ensure that all standards are kept.
With this said, I’ll just leave here the link to the “historical” vote in the ASF list
I know this post comes a little late and all but I still had to mention it on my blog. It turns out I am repeating the stunt again. After being turned down by Google last year, I decided I would try to apply once more this year.
Since last year I still had the change to get acquainted and get the logic of Apache Derby, I thought it would be wise to apply for the same project, and so I did. After all I do have an education on database management and also on Java, which are key for a project like Apache Derby. On top of it all there’s also my tutor from last year; despite not having been chosen I still had a tutor who helped me all the way through. Kathey Marsden agreed to be my tutor again this year and that is a plus for me because I know upfront what I can expect.
So, the application period is over and my application is submitted. The results should be out on April 20th and I have my fingers crossed for me to get picked