In some cases the following information is helpful: ...
Yes, but with the list getting longer, even fewer people are going to read it or follow its suggestions...
| [reply] |
I suggested the information is often helpful, they could be asked for as a 'one liner' rather than an individual bullet point for each:
"Post your OS, Perl (perl -v) and module (if relevant) versions"
| [reply]
[d/l] |
I absolutely agree the info is often helpful, as are the items in the original checklist. That's not the point. It's just that the more you ask people to do, the less they actually will do :)
As for presenting them on one line instead of bullet points, I don't think it'll make much of a difference. It's the number of items you have to take care of that matters, not only how they are visually arranged.
Anyhow, personally, I wouldn't expect things to change much with such a checklist, because those who need it the most simply aren't going to adhere to it anyway. Heck, they aren't even following the <p> and <code> formatting instructions (which are about as concise as it can get) right above and below the text area.
| [reply]
[d/l]
[select] |