| Subject: | Document where the right place is for this |
| Date: | Fri, 21 Mar 2008 14:15:05 -0700 |
| To: | bug-Moose [...] rt.cpan.org |
| From: | Michael G Schwern <schwern [...] pobox.com> |
My 34313 wishlist was closed with:
Show quoted text
> RT is not the right place for this. Please either send an email to the list or discuss this on IRC.
but that "bugs" and "features" go to separate places doesn't appear to be
documented anywhere. So perhaps the proper procedure for feature requests
should be written down?
Also adding a "resources" section to the META.yml would make finding the
mailing list and IRC channel easier.
http://module-build.sourceforge.net/META-spec.html#resources
Rant about bug vs feature tracking follows:
FWIW my personal philosophy is that once you separate the two you engender
confusion on the part of the bug reporter as to whether what they've
discovered is a bug or a feature leading to them not being sure what to do
with the request and just not sending it at all. The cockroach theory of bug
reports says that for every report you get there's dozens... hundreds...
thousands with the same issue who never send it. This suggests that one wants
to make reporting an issue as simple as possible. Making the user resend
their issue to another place is yet another point where they're likely to lose
interest.
The best example of effortless bug reporting is hiveminder.com. They have a
little "feedback" textarea on every page. Write down your feedback, click
send and done. As a result they get very good and very honest feedback.
--
Ahh email, my old friend. Do you know that revenge is a dish that is best
served cold? And it is very cold on the Internet!