This blog post just popped up in my rss reader and I thought I should post something about it.
Basically the blog post is about how questions asking people to identify something for them is not a good use of se. The looking-for-a-script is basically for questions where people ask other people to identify a certain script for them, based on features that we want.
In this question, it looks like we agreed that we should make catch-alls for different categories of software (e.g. forums, blogs, etc.). I think we should take that a step further and institute the following policy on script recommendation questions.
They must be community wiki.
Script recommendation questions can not have super specific requirements (e.g. "I need a forum script that can integrate with a blog and that has uses php and has the following list of features:"). Instead, the question must be asking for a list scripts that are a certain type of software, e. g. "I need a q&a script".
You must propose new looking-for-a-script questions on the meta first, so the community can evaluate them, and make sure that your question is a good one.
I'm against removing looking-for-a-script questions completely, because I think that when they meet these guidelines they are helpful to users.
Thoughts? NOTE: When we work out a solution to this, we should update the faq.