Up for adoption: dircproxy

I hereby announce my intent to retire from maintaining and developing this piece of software, of which I'm the original developer. However instead of just discarding it, I thought I'd put it up for adoption instead and make a bit of a competition to see who wants to be the next maintainer.

As I've yarned over-and-over, the reason I originally wrote dircproxy is

that it only used to take me 5 minutes to walk from my office to home, and I didn't want to have to disconnect from IRC, or miss what was being said. None of the other similar pieces of software did quite what I wanted, so I wrote my own.

Now I'm working from home, trying to earn a living doing the odd contract or two, I have no need for it so have stopped using it myself. This is obviously not a good position for an upstream to be in, I was already having the problem that many of the open bugs were in features I've never used myself so I was having problems tracing them.

So what I'm looking for is a responsible person or persons who use dircproxy and would like to become the new upstream for it. However, as I said, rather than just casting it adrift in the nasty wide world, I thought I'd make a competition of it.

So if you're interested, here's what you have to do:

• Make sure you have an account on the dircproxy Bugzilla, http://bugzilla.dircproxy.net/
• Make sure you have a copy of the latest stable source, ftp://ftp.dircproxy.net/pub/dircproxy/
• Or grab a copy of the unstable source from CVS http://www.dircproxy.net/cvs.html
• Start fixing bugs, attaching the patches to them and Ccing me when done.

As a general rule, "WISHLIST" patches should be against the unstable source and don't get quite as much merit as fixing the nasty bugs in the stable release.

There's no particular "closing" date, though if you're obviously working hard on a decent patch I'll wait for you to finish. The hardest working person or persons wins the keys to the CVS repository!