This hurts to write (licq was one of my very first packages) so bear with me, please. I also don't always have enough time to keep up with ddevel (I just finished clearing through a two thousand message backlog mostly by skipping most of it), so on this topic, please CC me. The short of it is that I'm under too much strain right now to do a good job, and since licq/gtk+licq are my highest maintenance packages, I need to pass them off to someone else. I'd like someone with at least a little packaging experience, who uses licq regularly, isn't afraid of running through different frontends, is on the licq developer mailing list, knows enough C/C++ to be at least able to read bits of code and patches, familiarity with CVS, and who has a fair amount of free time -- in short, someone who can offer at least what I should have been able to offer if things had turned out differently. If there's nobody who can provide this at the moment, I'll just keep plodding along. For what are possibly selfish reasons I'd rather I maintain licq poorly than have someone else maintain licq poorly. Also, despite the current legality of uploading SSL packages from the US, I'm inclined to prefer someone in the free world. Most needed right now: bug validation and triage (it's all over the map at the moment), coordination with upstream on g++3.x compilation fixes (especially with regards to hppa), examination of the recent CVS gtk+licq to see if it can be gotten to compile yet, possible examination of Jons GTK plugin to see if it can be gotten to compile as an alternative to the gtk+licq plugin, and a rework of the licq-plugin-qt/licq-plugin-kde split mechanics. After those things are dealt with, it might be worth looking into whether or not it is possible to get it to compile with support for both Dante/SOCKS5 and SSL at the same time, and adding a debconf infrastructure for dealing with upgrades that require a certain amount of manual intervention. I will be available to answer questions about previous packaging decisions and quirks in the package, but may be slow in responding to e-mail. If I take longer than a week, please persist in bugging me again. I probably should have done this some time ago, but couldn't really bring myself to do it. I apologize to anyone who has been affected. -- Zed Pobre <zed@debian.org> a.k.a. Zed Pobre <zed@resonant.org> PGP key and fingerprint available on finger; encrypted mail welcomed.
Attachment:
pgp78liuGAO55.pgp
Description: PGP signature