CyanogenMod 6.0 Released (Still No Galaxy S Support)
Just a couple of days ago, the good folk 'Cyanogen' released version 6.0 of their much acclaimed CyanogenMod. To my (and many other people's) sadness though, it still does not support the Samsung Galaxy S nor any of its other flavours (Vibrant, Captivate, etc).
According to a previous post by the same gentleman, Vibrant support (and hopefully all the rest, by affinity) might be coming to version 6.1. Until this version is released let's just hold onto that thought and pray they are serious about it!
In the meanwhile, maybe you'd like to give one of the Froyo builds a spin?
Samsung Galaxy S Gets Android 2.2 (Froyo) [Beta]
In case you were not aware yet, there are Froyo builds available out there RIGHT NOW for the Samsung Galaxy S. You just have to be aware that these builds are in fact beta builds released by Samsung and thus might still be a bit buggy and crash-ey. Still, it shouldn't break your phone. If anything you'll just have to reflash it back with Éclair which is perfectly possible and very safe.
So you want to give these Froyo builds a try? After all there are already three betas out there so it can't be that bad, right? Well, just read on for a walk through on how to get these builds and how to get them on your phone!
Tiago is now officially an ASF committer!
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
http://mail-archives.apache.org/mod_mbox/db-derby-dev/201008.mbox/<4C6F038C.7080708@sbcglobal.net>
Samsung Galaxy S Lag Issue (And How To Fix It) – Android 2.1 [Updated]
[Updated - Jump to the end of the post for a detailed walkthrough]
As some of my readers may know, I have recently traded in my Maemo-wielding Nokia N900 for a brand new Samsung Galaxy S. This move was led by several reasons that I am not going to go in detail in this post now but I did it and I was very happy with my new phone. In comparison with the Nokia it was super fast and best of all, it runs Android which is, in my opinion, a great mobile operating system.