David Golden wrote: > On Mon, Mar 23, 2009 at 3:56 PM, Michael G Schwern <schw...@pobox.com> wrote: >> I ask not for myself, I know the answers to this and they suck. I've bitched >> about this before and its not necessary to go into details again. I ask as >> Joe Newbie CPAN Author who just got his first pile of failure reports and has >> no idea what to do next. > > Michael -- I'm really tempted to create an auto-responder for any > Perl-QA email that mentions CPAN Testers and point out *AGAIN* that > there is a cpan-testers-disc...@perl.org mailing list where most of > the CPAN Testers hang out as well as most if not all of the CPAN > Testers module authors. (Yes, some of us monitor this group too.)
I feel the same way about test-more-users. Eh, perl-qa is low traffic. > (My abbreviated tangential rant: wouldn't it be great if someone would > update lists.perl.org or hand over maintenance?) Or make it a wiki. Who even maintains that? >> What there should be is simple instructions on how to get a message back to >> the tester. This should be a single link or email address. [1] > > This was discussed at length when we cut over from email direct from > testers to authors to a periodic notification service. It's harder > for authors to contact testers. The flip side is that authors don't > feel spammed. The vocal minority of those who shouted for an end to > spam were louder than those who shouted that they wanted to just be > able to hit 'reply' and send to authors. There seems to be a false implication here that in order to have an easy response you need to spam the authors. All I'm talking about is a mailto link in the report. But like I said, I don't care how it's done just so long as it's one obvious step from the report to contact the reporter. Or get nntp.perl.org changed to reveal the email address on demand. A captcha. Or there's the unimplemented individual reports option in the cpantesters author preferences admin. What does that need done? >> An immediate and relatively simple fix is to provide a single use mail >> address >> on the report. A hash of the reporter's name and some unique information >> about the report, perhaps something as simple as a UUID. The author mails >> that and its delivered to the appropriate things, probably the test reporter >> and maybe cpan-testers as well. > > Since switching from email to web-based submission is a major goal of > the hackathon this weekend, and thus we'll be moving away from NNTP as > an archive, we'll need to design a "report view" web page anyway, > which could include a method to contact the author or otherwise reveal > an email address in a spam-harvesting proof way. Can I put you down > as volunteering to design something, get group consensus and then > implement it? Sure, and the four other things I'm signed up for. Like I said to Barbie, all I want to hear is something's in the works. > You can start by adding it to the roadmap and hackathon project pages here: > > * http://wiki.cpantesters.org/wiki/Roadmap > * http://qa-hackathon.org/wiki/CPANTesters > > See you at the hackathon! :-) > > -- David > -- 124. Two drink limit does not mean first and last. -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army http://skippyslist.com/list/
