Skip to main content
edited tags
Link
Notice removed Draw attention by gnat
Bounty Ended with Shog9's answer chosen by gnat
Question Protected by CommunityBot
added 1 character in body
Source Link
gnat
  • 11.3k
  • 26
  • 149
  • 330

Suggest to expose close votes distinguished by reason in question timeline page after question is closed.

Purpose of this feature is to help in discussing cases of closure when knowing vote split would be useful to avoid unnecessary tension. "Oh no I would never ever close this as unclear! I swear I picked some other reason, it is not my fault!"

Related:

Exposing close votes in the timeline is probably the easiest of all options here: doesn't require backfilling data for close records, doesn't require adding stuff to the data-dump... If folks are happy to see their close votes exposed on an obscure page, that's actually feasible. Post a specific feature-request, please.

The reason we display a big banner with large text when a question is closed is to show the author and any passers-by that the questions isn't a good fit for the site. In the case of the author, we want them to know what they can fix. Throwing several reasons at them at once, especially if they're just top-level reasons without full explanations, isn't very helpful. How do you choose where to start if you see four lines of giant text screaming at you? You probably don't; you probably just walk away.

The close reason that receives the majority of votes is usually a good indicator of what the primary problem is...

Suggest to expose close votes distinguished by reason in question timeline page after question is closed.

Purpose of this feature is to help in discussing cases of closure when knowing vote split would be useful to avoid unnecessary tension. "Oh no I would never ever close this as unclear! I swear I picked some other reason, it is not my fault!"

Related:

Exposing close votes in the timeline is probably the easiest of all options here: doesn't require backfilling data for close records, doesn't require adding stuff to the data-dump... If folks are happy to see their close votes exposed on an obscure page, that's actually feasible. Post a specific feature-request, please.

The reason we display a big banner with large text when a question is closed is to show the author and any passers-by that the questions isn't a good fit for the site. In the case of the author, we want them to know what they can fix. Throwing several reasons at them at once, especially if they're just top-level reasons without full explanations, isn't very helpful. How do you choose where to start if you see four lines of giant text screaming at you? You probably don't; you probably just walk away.

The close reason that receives the majority of votes is usually a good indicator of what the primary problem is...

Suggest to expose close votes distinguished by reason in question timeline page after question is closed.

Purpose of this feature is to help in discussing cases of closure when knowing vote split would be useful to avoid unnecessary tension. "Oh no I would never ever close this as unclear! I swear I picked some other reason, it is not my fault!"

Related:

Exposing close votes in the timeline is probably the easiest of all options here: doesn't require backfilling data for close records, doesn't require adding stuff to the data-dump... If folks are happy to see their close votes exposed on an obscure page, that's actually feasible. Post a specific feature-request, please.

The reason we display a big banner with large text when a question is closed is to show the author and any passers-by that the questions isn't a good fit for the site. In the case of the author, we want them to know what they can fix. Throwing several reasons at them at once, especially if they're just top-level reasons without full explanations, isn't very helpful. How do you choose where to start if you see four lines of giant text screaming at you? You probably don't; you probably just walk away.

The close reason that receives the majority of votes is usually a good indicator of what the primary problem is...

Notice added Draw attention by gnat
Bounty Started worth 100 reputation by gnat
edited tags
Link
Notice removed Authoritative reference needed by CommunityBot
Bounty Ended with no winning answer by CommunityBot
Notice added Authoritative reference needed by gnat
Bounty Started worth 50 reputation by gnat
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link
Loading
Source Link
gnat
  • 11.3k
  • 26
  • 149
  • 330
Loading