Google is so nice to use “Not Selected” instead of “Rejectd” in the ranking my proposals. It just reminds my that Intel China replied my job application with the title” Rejection letter”, thanks god, they did not capitalize all letters. :-)

In all of the projects I’ve proposed, the favorite one is the collaboartion of KDEPIM and Google calendar. I was a little sad yesterday, since I thought it was a really good approach to address that problem until I found one student proposed almost the same way and accepted. Ok, it is good to see my idea is adopted even though I could not execute the idea. I might work on KDE GTD just for fun in this summer.

UPDATE: Dojo offers me two mentors for my proposal, highly possible without funding, I think I would take it.

UPDATE: Dojo manages to get the sponsorship from Mozilla Foundation and SitePen.

In the last post, we have descrbed the magic of SVN. Now suppose the following scenario:

• You travel a lot, and have to work offline in the flight frequently.
• You are a insane SVN user, the members in the team are quite annoyed by thounds of commit-notification, since most of them are quite trivial.

SVK is designed as the decentralized version control tool. It works as the front end of SVN, CVS, Arch and other version control system. SVK’s syntax is almost the same as SVN. If the svnbook were not licensed under Create Common, the author of svnbook would go to jail for the piracy. :-)

SVK adds three distinct command to do the job:

• svn mirror — Mirror the remote SVN repository to the local depot
• svn push — Commit the latest local depot to the remote repository
• svn pull — Get the copy from the remote repository

SVK is still quite new to me. I would like to update this post later.

SVN, aka Subversion is regards as the “time machine” for the software developer. To make things for easy understanding, suppose you are “working” in the Civilization III:

• Save the Game — svn commit commit the change to the repository.
• Load the Game — svn revert You can always rollback to the previous working copy.
• Load the Game 200 years before for the failure to build Great Library — Yes, you can svn merge the difference of now and history, then bring the history to the current working copy.
• //Sigh.. I have to fixed my mistake 200 years before, then redo almost the same things else — For SVN user, you can diff the modification from 190 years before to now and applied to the above copy.
• Damn, I lost all the .SAV files! — You can leave the SVN repository in the remote host, like sourceforge.net or tigris.org.

This is what we call Version Control. PyAWS is under the SVN version control at sourceforge.net.

It took me almost 6 hours to finish the first draft of my personal resume. Great thanks to Isaac Z. Schlueter for his generous XHTML/CSS resume template. Hope his magic template also bring me good luck.

I think this resume still needs more polishment, so any feedback is greatly appreciated.

UPDATE: Greate thanks to Xi Su’s suggestion on the resume.

Expose is a sweet feature to switch applications if you have opened thounds windows in your desktop. In the FOSS territory, here are two competitors: Skippy and expocity.

Both of them are in portage. Personally, I prefer skippy since it is has less dependancies, only X and imlib2. The only drawback is the lack of fancy animation, and if you want to more advanced feature, like live snapshot, you need to do some hacks to enable composition of your X11 server. Here is a screenshot of skippy in action: