What is community wiki?

Question

We have somewhat of an on-going problem in that "community wiki" is not perfectly defined (and even so far as it is defined in the stackoverflow world, it's conceivable that it should have a different meaning in our context).

Questions such as

• http://stats.stackexchange.com/questions/1610/is-there-a-way-to-remember-the-definitions-of-type-i-and-type-ii-errors
• http://stats.stackexchange.com/questions/22/bayesian-and-frequentist-reasoning-in-plain-english

do not have objective answers. Yet, they "feel" different to me than questions like

• http://stats.stackexchange.com/questions/3/what-are-some-valuable-statistical-analysis-open-source-projects
• http://stats.stackexchange.com/questions/726/famous-statistician-quotes

So the question is: how should we define "community wiki" for our site? Should "list" questions be community wiki, but otherwise subjective questions that are looking for a general answer be left alone?

One reason that I raise this is that making a question "community wiki" removes some of the incentive to provide great answers, but IMO questions such as the former two above require effort and good answers should be rewarded.

Answer 1

Here's my perspective:

If the asker is looking for a singular right answer (even if that answer won't work for every user, such as in the case of my question, 1610), then it shouldn't be community wiki. In the case of my question, it shouldn't be community wiki from the get go since I (the asker) have the intention of selecting an answer as "the right answer" - it's the answer that solved my problem. Now, if it turns out that there truly isn't a right answer or a single answer that helps the asker, then it should be up to the asker to come back and make it a community wiki question to denote that there actually isn't a single right answer to solve the problem, but it's actually any (combination of) or all of the posted answers.

If the asker is just looking for suggestions or a collection of resources, that should be community wiki. The asker isn't looking for a singular solution to his/her problem - the answer will be a collection, taken as a whole. People contributing answers aren't as an individual helping the asker reach an answer, but contributing a small piece of the puzzle (a single book, a quote, a tool, a software program). The asker might find a single answer that answers his/her question, but the answer really doesn't mean much by itself.

Answer 2

I don't think Thomas's question should be community wiki, because it is a focused question. There can be more discussion on the other one. The main reason is that it is not a question. Indeed, as the question is formulated we see the author has already his answer and is interesed in getting people's view. I think the question about bayesian is borderline, this other one is also borderline:

http://stats.stackexchange.com/questions/130/clojure-versus-r-advantages-and-disadvantages-for-data-analysis

Finally I guess we should keep them as non CW but remember that this is the border :) (a question can't be less focused)

The reason why a question asking for people's view (and not a question asking for an answer) should be CW is mechanic.

• It generates a lot of reactions because when you have an answer it si likely that everyone has an answer.
• People are happy to find a place to talk and vote up.
• this type of question is encouraged (because you gain a lot of points) and thousands of answer are given.
• stat.stackoverflow becomes a forum.

Do we want a forum ?

Answer 3

I like what's been said already. In general, I favor approaches that result in greater sharing of information.

It seems that CW content tends to decline unless it's about jokes, quotes and such. I'd rather see people contributing more for points or whatever. I admit that I'm less concerned with subjectivity, etc. It's especially hard for me to see statisticians or data analysts agreeing on the one view to bind them all. Let downvoting do the work. In the extreme cases where discussion begins to devolve to nonsensical proportions, I favor moderators acting to close the question.

Very generally, my modest proposal is the following guidelines:

• avoid a rush to judgement
• if you think a question should be closed, err on the side of asking for it to go CW
• if you think a question should go CW, err on the side of letting the community express disapproval through downvoting

Answer 4

I think the community wiki FAQ on cooking.SE answers this question excellently. Since both questions and answers can now be edited by anyone, regardless of rep (albeit with moderator approval for those of us with low rep), there is almost never a good reason to use community wiki. This even applies to most list questions.

Considering the ability for anyone to edit, the only value in community wiki is to deny reputation. This is potentially useful for avoiding rep farming, and filling the site with relatively useless fun list questions. Many questions of this type should just be closed anyway.

Community wiki is also potentially detrimental for the same reason: once there is no rep gain, there is less incentive for someone to spend their time writing a good, detailed answer.

Because community wiki can not be unapplied, it should be used judiciously. I would suggest that we adopt something like the cooking.SE guidelines linked above. Thoughts?