It's the weekend now but I have a awful feeling that I won't have all much time to enjoy it. I'm well behind schedule on the parser/interpreter, so I think a late night hacking session beckons - caffeine and MP3s at the ready :-)
I'm now certified at 'Apprentice' (thanks voltron, alisdair, pjones and sh).

The talk by Stephen Tweedie was very good, he was an excellent speaker and was able to pitch the technical level well, so that everyone was kept interested - quite an achievement considering the diverse skill level of the audience. He also offered an interesting avenue of investigation on why my MP3 jukebox doesn't play properly - perhaps it is the lack of DMA and not the lack of CPU power (it's a P60).

I had my first look at the database that I'll be writing the front end to, so if I get the chance I'll try out some JDBC on my PostgreSQL database, and experiment with some XML tools. All I need now is SSH access to the Oracle database in University and I'll be happy.
At the moment I don't think there's much chance of having the project open sourced, but I'm looking for reasons, like GPLd killer applications/libraries I could use etc... The main personal reason I have is that I don't want the project to die after I stop work on it. I've seen several projects on the web which are very promising, but still have a few rough edges. The developers have done an enormous amount of excellent work creating the project but no one will use it as it still has some annoying bugs. If it were open sourced then these would soon be sorted and the application would become a useful tool.
I believe that query tool I am writing could be of use to many people if it were in a finished state, but probably at the end of the project it will still need work. In my opinion the best way of getting this last hurdle overcome is to open source it.

I think that's enough for today... time for work; where are those Penguin Mints.