Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQThe FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some peoplesome people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CWFAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topicsthe FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.

When to do it

The main (perhaps only) reason to mark your own question as CW is if you post a topic which you intend from the begining as a Wiki topic.

Other types of question which should be marked CW from the begining, if they are even asked at all, are:

  • Trivial 'poll' questions: for example, "Do you use version control? {yes/no}"
  • Questions intended as a 'joke': though such jokes are increasingly rare now on StackOverflow
  • 'Soft' questions, whose answers neither reflect nor contribute to people's professional and technical know-how.

However new poll questions often get closed, as do jokes, discussions, and 'soft' questions, whether or not they're marked as CW.

When not to do it

Except as above, questioners need not mark their own questions as CW. Instead, any and all questions that are worth asking and worth trying to answer are worth potentially being given rep for. In particular, the following are not good reasons for marking a question as CW.

Questions which can have more than one answer -- The FAQ says, "this is a place for questions that can be answered", but it doesn't forbid questions which have more than one answer. Questions whose answers are subjective perhaps shouldn't be asked at all (especially if argumentative), but otherwise a question's having more than one answer is not a reason for the questioner to make it CW (except when it's a "trivial poll" question as mentioned above).

Questions which will be downvoted -- some questions will be downvoted for one reason or another. In this case you should ask a better question or not ask it all: don't make the question CW just in order to escape being given negative rep.

Questions which will be upvoted -- some people, when they don't like a question for one reason or another, demand that the questioner should mark the question as CW so that the questioner doesn't get rep for it; however:

  • If you don't like a question then, instead of demanding that it be CW, it's better to ignore it without upvoting it, or downvote it, or vote to close it.
  • Upvotes for questions are only worth +5 now (no longer +10): so, question's being upvoted isn't so important any more
  • There are other mechanisms (e.g. sufficiently many edits, or moderator actions, as listed in the FAQ about CW) which allow a question to become CW later: there is therefore no need to demand that a question be CW from the begining.

Questions which become FAQs -- people used to use CW to create the FAQ topics: this kind of topic and discussion has since been migrated to Meta. Outside of joke/poll style threads, CW was largely made obsolete with the creation of Meta.

Summary

A question should not be marked CW if it is possible to write valid, helpful and knowledgeable answers which contribute to SO. Even if there is more than one valid answer (in open-ended questions), individual answers may still have value, and so they deserve the rep gain when they're upvoted. Marking such a question CW just discourages people from putting any effort into their answers.

  • It's usually sufficient to have the other existing mechanisms which automatically convert a question or an answer to CW, after it's asked or answered.
  • There's usually no reason for a question to be CW when it's first asked.
  • It's virtually never appropriate to tell the questioner to mark their question CW.
Fixup of bad MSO links to MSE links migration
Source Link
Fixup of bad MSO links to MSE links migration
Source Link
Loading
Migration of MSO links to MSE links
Source Link
Loading
Incorporate the comments made by Gnome
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading
incorporate from jalf's answer
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading
added 1168 characters in body
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading
edited body
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading
added 159 characters in body
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading
Post Made Community Wiki
Source Link
ChrisW
  • 10.5k
  • 1
  • 33
  • 67
Loading