On Thursday and Friday, I took time off work to visit Bristol for the GNU Hackers' Meeting 2008. Around 20 people attended - obviously these were all people contributing to GNU, but (surprisingly) I didn't feel too much like I was surrounded by giants. Instead, it was all quite relaxed; most people there seemed rather like me - with a mild caffeine addiction, permanently short of spare time, and just trying to improve their small projects as best they could. ...

After much anticipation, the free-as-in-freedom version of Sun's Java JDK has arrived in Debian's `main' section. There are still a few bugs in the packaging, but these will be ironed out before the lenny release. Various other useful packages still need to adapt to its presence, but many will be able to move from the `contrib' section into `main' as well. Going forward, this makes Sun's Java platform quite attractive for developing future free software applications. There is a reasonably performant implementation now available in most distributions, that will receive security updates, has a good team of developers behind it, and already has a large community of people with skills in the language. If static versus dynamic typing becomes an issue, Jython might offer a nice competing implementation of Python. We might one day get to see what this `Groovy' thing is all about. In terms of GUI applications, Andrew Cowie's new java-gnome 4.x bindings will allow truly native integration with the rest of GNOME - or stick with plain Swing for cross-platform portability. ...

An update to Debian's gnu-standards package is now in incoming. This package contains the GNU Coding Standards and the Information for GNU Maintainers document. It is now in the `main' section rather than `non-free', so is officially part of the Debian system. This has taken several months; at the end of December I asked whether the maintainers' document could be relicensed. RMS evidently approved, because the licence was changed in January. Then there was the small matter of updating the Debian package; I prepared an update, but wasn't quite clear on whether I was preparing an NMU or a normal upload, so stalled for a while. Last month the package became orphaned, so I quickly grabbed an ITA, and started working again. KiBi was very helpful with pointing out all the remaining cruft in the package, and he generously sponsored the final result. Then we just had to wait for it to get through the NEW queue. ...

Blue and White G3 PowerMac on eBay, collection only: £10. Train fares to and around London: £26. Fixing an annoying PowerPC f-spot bug: priceless. It weighs 13kg, apparently, and my arms still ache. Thanks to Anton and Dan for letting me stay at their place on Saturday night, and use their fast net connection to download Debian packages.

The first rule of licence club is, you do not talk about licence club. The second rule of licence club is, you DO NOT talk about licence club. If a copyright holder says stop, gets confused, is bought out, the licence is over. Only two parties to a licence. One exclusive licence at a time. No CDDL, no Jörg Schilling. Licences will go on as long as the copyright is enforcable. If this is your first night at licence club, you have to hire a lawyer.

Some small victories: You can now install devscripts-el without needing to install elserv, an http server written in emacs lisp and Ruby. (The devscripts-el package provides various useful emacs commands to help with Debian packaging.) This is good, because I don't need Ruby for anything else. It is now possible to use irssi's default theme on terminals with a white background, at least in Debian. I found that in bright sunlight, black-on-white terminals were actually more visible on my laptop screen - but when using IRC, I couldn't see who was using /me any more. Apparently upstream are yet to be convinced of the wisdom of not hardcoding white into their themes.

This evening I visited Rugby Library. Apparently I had not used my Warwickshire library card for 991 days - that was from when I lived in Leamington Spa. It is probably quite a while longer since I last borrowed books from Rugby. To be honest, I was quite fond of the old Victorian library building. Unfortunately, that one closed in 1997 and was demolished. And I suppose the £5.5m new one looks nicer.

Increasingly I am asked how things are going at work. Unfortunately, I struggle to give a meaningful answer in conversations with "normal" people - I don't know how to begin to explain that this afternoon I set up a pbuilder environment that lets me build Debian packages for our customised etch-with-backports i386 distribution using my amd64 machine running Debian sid. Or that this morning I ran into some interesting problems with dpkg-shlibdeps and symbol versioning in lenny when trying to downgrade some dependencies to 'Suggests'. "Er, yeah, it's going fine." ...

Another potential response to online complaints about free software is "FSFI", meaning "It's free software, fix it". This is the next level up from asking someone to link to their bug report - it places the sole responsibility for fixing the bug onto the shoulders of those who complain. Sometimes this can be reasonable - but expecting every user to be able to fix every problem themselves is not. There was a link today on LWN to an article claiming that it is strictly the software which is free, not the users - the users must abide by the restrictions of the licence, so cannot distribute proprietary derivatives, for instance. I would have claimed exactly the opposite; software does not have a will that can be frustrated. It is the users of proprietary software who are not free to study, to improve, to share. The term "free software" misleads in this respect; the ethics are all about what the users can or cannot do. On the other hand, we might reasonably talk about a "free society", and would understand that its citizens were free as well. ...

With the rise of the blogosphere, a greater number of people are now free to post their thoughts to the world - and because of the nature of the medium, there are a fair number of people writing about their experiences with computer software. Most software is not perfect, so some proportion of those experiences will be negative. In the special case of free software, all end users have the freedom to study and modify the source code. (It is easy to forget, having used GNU/Linux for a few years, that the licences of most proprietary software do not even give you the right to run the software in a debugger.) This does not imply, however, that the end user is necessarily capable of debugging any problems they run into themselves (although they do have the freedom to pay someone else to do so). In general, users will rely on the original developers of the software to fix any problems - and a good way to get the developers' attention is to file a report in the project's bug tracking system when there is one. It is unlikely that the developers will learn about problems through any other means. ...