Potentially Predatory Pre-Announcement of Possible Vaporware (zinq-djbdns-0.01)

    When Qmail went public domain, I hatched a scheme to fork my own
version of it.  I came up with a not-so-clever name for it: Zinq (Zinq
is not Qmail).  Once I got into importing the source into Subversion
at SourceForge, I realized  that Qmail isn't much fun without
ucspi-tcp and daemontools, and there is a lot of code commonality
(Dan's stdio replacement(s)) with djbdns, too.  So I imported all
four.  Suddenly my not-so-clever name was even less clever.  Frak it,
I thought, I'll come up with a really terrible bacronym later.  After
almost a full year of slacking off, I have finally released ucspi-tcp
and daemontools packages via SourceForge (zinq.sourceforge.net), and
I'm gearing up for djbdns.
    For now, I'm trying to keep the changes fairly minimal.  Well,
apart from converting to Autoconf/Automake, anyway.  For ucspi-tcp and
daemontools, the bare minimum list was pretty obvious:  fix up the
errno thing and rip out the default blocklist for rblsmtpd.  For
djbdns, I'm not quite so sure where to draw the line.  I've been out
of the 'hosting my own domains' business for a while now.  Even before
I'd switched to letting Google run most of it, I'd stopped paying
attention for years...which I could get away with, running djbware on
a heavily firewalled network.
    At the moment, the only things on my list (aside from
autotoolization and errno) are a fresh list of root nameservers and
maybe the SIGPIPE fix.  Any nominations for anything else?  Flames?
Insults?