I was just thinking about all the projects I've contributed code to in the past and thinking, "Huh. That's quite a sizeable list."
The list goes something like this:
Being only one post away from breaking my "most posts in a month record" and somewhat making up for the dearth is posting last month, I present to you "Taming the Tiger!". Er, Leopard that is.
This January, God willing and KDE E.V. paying, I'll be in Jamaica for the 1st (hopefully) annual Camp KDE conference. Camp KDE spun out of the KDE 4.0 release event which took place in Mountain View, Cali at Google's place. Legend has it the organizers of the event realized that there were a lot of people who weren't going to the akademies in Europe because they a) couldn't afford it b) had other engangements at that time. I can relate to both points as I was always either in school whenever they had akademy (scheduled too close to end of semester/exam season) or couldn't afford to go.
When last we spoke I left on a rather uncertain note. But will it work...
I asked. The immediate answer to that query was No. It will not.
Being far too persistent with these things I kept on working until the answer was Yes. I have defeated you, vile beast.
Yes, dramatic. I know.
What do you do after working on something for 16 hours? Take a break. A long break. For 4 hours on Friday and 12 straight hours on Saturday I was working on getting my installer package ready. The installer package in question had precious paylod: a beta version of Amarok 2. I finally got it in a state I was comfortable with and released it into the wild. It took quite a bit of work, far more than expected, to get the installer working to my satisfaction. There were some things which I required it to do, or not do, before I was comfortable with releasing it; things which I list below.
Make what so? OS X packages of course! This weekend (actually Labor Day for all us Yanks) a little rose pricked me and reminded me about those packages I was supposed to be making. The friendly poke gave me the activation energy needed to get over the hurdle and get the job started again. That's a little in-joke for the Chem geeks in attendance.
I remember when I was in college, around either amaroK 1.2 or 1.3 release time, when I first found out about (and was invited to) the amarok dev channel. I don't remember exactlty why, but muesli let me in on the secret. Maybe it was because I was helping out with the docs, or maybe he just wanted to talk about music without the constant distraction of user questions interrupting us :-) Ah yes, good times back then. He turned me on to the awesomeness of Daft Punk and Ol' Dirty Bastard's "Baby I Got Your Money" if I recall correctly.
Continuing from the Superman theme of the previous entry (despite the Narnia themed title) I've overcome impossible odds to realize the obvious about half an hour ago. What mighty revelation has been bestowed upon me?
So the boss wants me to design some siRNAs, the uncle wants me to create an email account and do other resumé related tasks. This is while I want to figure out if I can get phonon-qt7 to load files via kioslaves. Let's not forget that I have to get utilities and insurance set up for the new apartment. Apparently I'm a miracle worker because this was sprung on me Wednesday and ideally needs to get done before Friday. Did I mention that I actually officially start work on Monday, not Friday?
So today I figured out pretteh cuncloosevlay, that the issues amarok was having with the phonon_qt7 backend were wholly amarok's fault. There endeth my involvement with that little debacle. Now we need someone with phonon_foo to come fix it. Anyone foolishly hoping I would be the one to buckle down for the summer and dive into both Amarok and Phonon APIs will be pleasantly disappointed as I have absolutely no intention of doing so. The reasons for this are two-fold: 1) I have a job now which I need to begin preparing for, and 2) I don't believe I can do it.
illogic-al.Org