# from David Golden
# on Wednesday 10 September 2008 04:07:

>I would suggest just including a link to the wiki.
>It has information on how to get set up to send tests and they can get
>to the reports page from there.  Having a choice of two websites
>decreases the chance they'll look at either.  (Economists have
>determined that choice is stressful.)

Ok, let's get stressed-out then...  http://wiki.cpantesters.org/

  choice 1:  "Home" - takes me to where I already am!
  2:  "RecentChanges" - huh?
  3:  "Sign up or login" - maybe that's what I should do?
  4:  "history" - NotSoRecentChanges?
  5:  Search - try "install" ;-)
  ... Lots of text ...
   9: Mail barbie - maybe I should try that?
  10: Prologue 
  11: Why Is Testing Important? 
  ...
  16: GettingStarted - hmm...  I need a cluster?
  ...
  18: CPAN-Reporter Installation

And so on ;-)  The wiki is a bit noisy as quick intros go.  Especially 
if this is an interruption to "I was about to install this module", so 
we're quickly hitting the "no, that's a big distraction" threshold.

And on the subject of interruption...  this is part of your module 
documentation (I hope it's toward the end), so keep it short and sweet?

"
=head2 CPAN Testers Reporting

Please install CPAN::Reporter so that a report of the installation and 
test results can be seen by the author and other users.  Please see 
L<http://wiki.cpantesters.org/wiki/QuickStart> for instructions and 
more information.
"

Or so?  Then just have the QuickStart page *start* with the two most 
common setups, followed by the "oh this is neat, tell me more" links.

And, why is 'o conf init test_report' needed if I'm just going to take 
the defaults?

That's just my "being the user" assessment.  You could try interrupting 
an impatient co-worker and see what they think ;-)

--Eric
-- 
"It is impossible to make anything foolproof because fools are so 
ingenious."
--Murphy's Second Corollary
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------

Reply via email to