Timeline for Vote Early, Vote Often
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2012 at 14:47 | comment | added | yannis | If the policy changes (probably to become a lot stricter), it would be an example where people decided that we just don't like books questions, and told us about it with their downvotes. The same can happen here, if some questions are technically on topic (requests for review of working code) but, for example, the code is trivial, we can show that the questions are unacceptable with our downvotes. | |
| Oct 11, 2012 at 14:45 | comment | added | yannis | Well, to give you an example of what "unacceptable for this community" means, on Programmers (a graduate and fairly mature site), we had a policy of accepting some book requests. The matter was discussed on Meta early on, consensus was reached, etc. But then it appeared that most book questions we were getting were crap, and people downvoted them to oblivion. Right now, after noticing that for quite some time, we are discussing about changing the policy... | |
| Oct 11, 2012 at 14:41 | comment | added | mseancole | @YannisRizos: Still a bit misleading "unacceptable for this community". But I agree with your sentiments and will try to be a bit more active in the other tags. Its still a good point and you've already got my upvote :) | |
| Oct 11, 2012 at 14:35 | comment | added | yannis | Anyway, what I want to encourage is this: Go and read every question and answer in the tags you are active in, and vote on them if you feel they are worthy of your (up/down)vote. There are probably quite a few posts you've missed even if you are very active on the tag, vote, vote, vote! When you are done, start reading Meta questions from the very first one, and vote, vote, vote! | |
| Oct 11, 2012 at 14:28 | comment | added | yannis | Hm, that sentence applies more to the very early days of Beta, Code Review is way past that point. That said, it's the very next sentence we should focus on: "Voting shows what constitutes a well-formed question and what is unacceptable for this community.". | |
| Oct 11, 2012 at 14:26 | comment | added | mseancole | Admittedly, I feel bad about downvoting off topic questions, so it has to really be off topic, or violating some other rule for me to downvote it. Usually I just inform the OP that his question is off topic and that I'm voting to close it. Sometimes I also leave advice on how to change the question to be more on topic, such as adding code or changing wording. If they then change it, I do my best to then answer it. | |
| Oct 11, 2012 at 14:20 | comment | added | mseancole | @YannisRizos: Directly from your post: "Voting allows the community to determine what topics are allowed and what are not." Unless I am misinterpreting that. Besides, this is a phenomenon I have directly observed. There are a bunch of questions, at least in PHP, that I have seen upvoted purely because they were on topic. In fact, EVERY question that is on topic seems to have at least one upvote, and every question off topic seems to have at least one down before it is closed. Or maybe I'm just seeing things. | |
| Oct 11, 2012 at 14:06 | comment | added | yannis | We don't upvote a question for being on-topic, and similarly we shouldn't downvote it simply because it's off topic. Votes (up/down) are feedback on the quality of a question, not its topicality. If it's off topic, vote to close, if it's on topic, well... don't vote to close ;) I'm in no way saying we should go for quantity (of votes) instead of quality, but we severely lack in voting activity compared to younger sites. | |
| Oct 11, 2012 at 13:59 | history | answered | mseancole | CC BY-SA 3.0 |