thread titled: Taking over Net_DNS on PEAR QA Mailing List

There is a back and forth for a while on the PEAR QA Mailing 
List about getting Net-DNS back into a mantained state -- I 
assume this would carry the whole gamut of cutting new 
releases, taking patches, etc.  (2010-03-17 to 2010-04-13)

So near as I can tell, it sort of petered out and died, 
without a new release being cut and rolled, known patches 
applied, etc

We run a locally forked Net-DNS (there is a problem in the 
AAAA code validation regex in that it permits malformed IPv6 
variants), and some other fixes.  Also there is a LOC patch 
(revised) floating about, that we had to fix and extend, as it 
has 'issues' as to actually working ;)  [1] It parses the 
binary data rx from a nameserver, but as we tried to use it, 
we found that it does not apply cleanly, does not parse the 
textual data fields, and cannot submit new records through the 
update mechanism TO a nameserver

I am reasonably indifferent who takes over code maintenance, 
so long as fresh cuts are happening [selfishly, so that I can 
get out of maintaining a local fork ;) ] and the code works; 
I understand the desire to solve some other problems as well 
(slow tests, learning coding style, etc), but really, aren't 
these orthogonal to that?

I fumbled about a bit on trying to set up an account, but it 
seemed that filing a bug was the only gateway I could find for 
that presently.  (I would like to be able to 'join the 
conversation' on that LOC patch, for example) This may be my 
unfamiliarity with the process, and so I write directly while 
this is fresh in mind

hoping to hear back ...

-- Russ herrold

[1] http://pear.php.net/bugs/bug.php?id=11665