----- Original Message ---- From: Adrian Howard <[EMAIL PROTECTED]> > > Except that there needs to be some movement on TAP again. There > > was a flurry of enthusiasm, upgrading the perl-qa wiki with plans > > for TAP::Harness, talks about subsequent versions of TAP, but then > > it died. Hell, I have the core in place to move on this, if only I > > could get an official blessing on it. Having heard nothing, I just > > gave up. > > I'm not sure who's the "official" here? :-)
I don't know that anyone is 'official', but I suspect that most in the community who have any idea about perl's qa stuff would probably look to Schwern and Andy. They're kind of the keeper of the keys on the core modules here. I'd like to see more work done on this, but I've not really received feedback (I don't think Shlomi has either), even though, as mentioned, I've done most of the work necessary to put a TAP::Harness in place. In short, many of the gripes of the Perl community about the known limitations of our testing framework could be mitigated if can get momentum on this again. However, OSCON just ended, Schwern has a new job, Andy has other (good) projects that he's pursuing and work here has stalled. I can't say I blame them because I certainly have bursts of energy followed by periods of needing to recharge, but I don't know what to do. If I've spent a lot of time building something that is deemed unsuitable for the future direction of TAP and the testing framework, I really don't want to continue working on it. If it *is* suitable but needs some work, I'd like to know that, too. Cheers, Ovid
