Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You may already be planning on this, but I'd just like to explicitly bring it up.

    Please also address the "barrier to enter", and consider lowering that particular bar.

    Since so many bug reporting guidelines and systems require a significant investment on the part of the user. If I'm simply evaluating some software, and I most likely will not be using it again, I won't be bothered to register, submit a bug and follow through with all the steps.

    However, if there is a *simple* and well-addressed mechanism for submitting problems I'm more inclined to do it.

    To put more personal context on my request, I'll share an incident that illustrates this from my real history. I was evaluating puppet and became frustrated at the stupid error messages. Looking at their bug tracker, there are no guidelines or any links labeled, "Report".

    So, guess what? I didn't do it and don't have a shred of guilt or remorse. Why would I bother? I wasn't impressed enough with puppet even if the error messages were fantastic to be. Instead I posted on twitter about it, with enough detail on the particular error message (involving template errors).

    Response? "Here's a link to our bug tracker, submit an issue". Fail. Er, I mean, #fail.

    --
    Killing two stones with one bird.