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

use Perl

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.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

A Small Feature Request (Score:1)

by jshirley (7627)

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

--
Killing two stones with one bird.
I really like the analogy (Score:1)

by xsawyerx (8978)

Straight off the bat.
People would often reply to that with "If you don't want to step in shit or god-knows-what, don't step on my porch" which is sort of equivalent to the ol' "this is free software, leave me the fuck alone".
Software is like plumbing (Score:2)

by jonasbn (1153)

You have probably seen this blog article, but it does address some of the same aspects as your talk:
http://blog.arlim.org/2010/02/28/software-is-like-plumbing/ [arlim.org]
- Re: (Score:2)
  
  by schwern (1528)
  
  Nobody cares about it until it doesn't work. Exactly.
The correct etquette (Score:1)

by singingfish (7494)

Now, I was under the impression that the correct etiquette when placing a turd on someone's doorstep was to put it naked on top of some crumpled newspaper, set light to the paper, ring the doorbell and run away fast.