Debian's navel gazing

Debian is my favourite distribution of GNU/Linux. It's a well respected and well known brand, although I was almost stunned while on business in London last Friday to meet someone who knew about Suse, and Red Hat but wasn't even aware of the existence of Debian. I like Debian's astonishing infrastructure, and its community led approach. It has been on the verge of releasing its next stable version, Lenny, for some time. I've been waiting for that freeze to end to have my debian packages of OPUS uploaded, since there is currently no real rush and I wanted to do more "upstream" work on them. At that point I wanted to start the long path to DD status (via maintainer).

Noodles, who is a DD, has recently commented on his frustration that Debian procrastinates at the end of every release cycle. This seems to be true, and internecine war always seems to erupt over issues that should have been solved long before (or alternatively after) the release. I'm also sympathetic to his suggestion that Debian's voting procedures could be improved.

Reading through Planet Debian today, I am more depressed than ever. Debian's secretary has resigned over voting issues and the vitriol unleashed by them. I'm not making any comment on that. There is already a constitutional pathway for an interim secretary, but now, the project can begin to rip new wounds in itself over the resignation, rumours of expulsion procedures and what to do next. What to do next is damn important, but so is the release.

I was in Plymouth in September with Lenny installer beta 2 CDs with Lenny images that wouldn't even install on the new hardware in a problem frustrating similar to one I found months before (Ubuntu, derived from Debian, embarrassingly did so without problems). I dare say that issue has been fixed (I can no longer test it), but it's a horrible reminder of how a prolonged freeze can lead to an OS that can be born obsolete in the sense that it can't install on newer hardware.

Follow me!

Leave a Reply

Your email address will not be published. Required fields are marked *