5

When you think that a feature request in a question should not be implemented (e.g. because you do not agree with the motivations provided) should you do either/both:

  • Downvote the question, so that by keeping a low score, it's clear it should not be implemented? Or
  • Answer motivating why the feature request is not valid, or upvote an already present answer?
Improve this question
19
  • Just hang around meta and your will see how the regulars act. That should give you your answer over time. There are far to many variables to answer. You could stop both, or either, or neither. All depends.
    – psubsee2003
    Mar 28, 2015 at 1:42
  • @psubsee2003 I can see only total scores, not by how many up and down votes was composed.
    – Antonio
    Mar 28, 2015 at 1:44
  • @psubsee2003 Many might explain in the comments why they disagree, but that won't say if they downvoted or not
    – Antonio
    Mar 28, 2015 at 1:46
  • 1
    You don't need to see vote splits to see how people act. Don't be so worried about how to act right away. Just pay attention and you'll figure it out. The idea of when to vote, answer, comment, or some combination of all 3 will come with experience
    – psubsee2003
    Mar 28, 2015 at 1:49
  • 1
    @Antonio: See How can I see the number of up / down votes on my own posts without 1000 rep?
    – Werner
    Mar 28, 2015 at 1:50
  • @Werner, thanks, but Psubsee2003 suggested to study the general behaviour of regulars towards feature requests questions, and I can only do that by checking questions asked by other people.
    – Antonio
    Mar 28, 2015 at 2:01
  • @psubsee2003 And this question got downvoted because...?
    – Antonio
    Mar 28, 2015 at 2:10
  • @Antonio: I know that. You mentioned though that you can't see up/down-votes per post, only (total) score. The linked post shows how you can achieve this.
    – Werner
    Mar 28, 2015 at 2:38
  • @Werner Only on my own posts, correct?
    – Antonio
    Mar 28, 2015 at 2:44
  • 1
    @Antonio: No. Timeline viewing is available to all.
    – Werner
    Mar 28, 2015 at 2:46
  • @Werner Amazing! :)
    – Antonio
    Mar 28, 2015 at 2:49
  • 1
    possible duplicate of When should I vote?
    – Patrick Hofman
    Mar 28, 2015 at 12:43
  • @PatrickHofman I believe there the answer was very hidden (in a secondary answer), while here it's very clear, but ok.
    – Antonio
    Mar 28, 2015 at 20:12
  • @ant true. I added it a while ago since it was missing from that post. It is in like with the faq though.
    – Patrick Hofman
    Mar 28, 2015 at 20:42
  • @Robert: Why was this reopened?
    – Patrick Hofman
    Apr 8, 2015 at 15:04

1 Answer 1

Reset to default
8

The "What's Meta" page says:

On posts tagged feature-request, voting indicates agreement or disagreement with the proposed change rather than just the quality or usefulness of the post itself.

(Emphasis in the original.)

People are voting such posts to indicate whether the feature should be implemented. You can vote like other folks do.

As with all other votes you cast on SE sites, it is not necessary to comment or answer when you vote. My personal guideline as to whether to answer is: a) should the post be answered, and b) has no one already provided the answer I'd give? It is hard to give a comprehensive set of rules regarding what post should be answered but in brief if the post is well-written and the proposal has a fault that the OP is likely to not have foreseen, then it merits an answer.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .