Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish between resolved/closed discussions #62

Open
ewinslow opened this issue Aug 12, 2015 · 1 comment
Open

Distinguish between resolved/closed discussions #62

ewinslow opened this issue Aug 12, 2015 · 1 comment
Labels

Comments

@ewinslow
Copy link
Contributor

Right now there is a way to "close" discussions (i.e. not accepting further comments), but not to mark them as "resolved" (i.e. no longer needing attention).

If we introduced a concept of "resolved" discussions, that would allow us to list only unresolved discussions in the main view, hopefully resulting in folks getting answers faster. If we listed least-recently-active first, this could remove the temptation to "bump" questions, since bumping would actually move you back to the bottom of the list and be counter-productive, making it less likely that you actually get an answer. I've seen a lot of bumping lately and resisting the temptation to scold people. I think a design fix would be better in this case than a social fix.

Of course, we'd have to let tickets "fall off" after a certain time going unresolved, accepting that they will never get a resolution.

@ewinslow
Copy link
Contributor Author

Perhaps we could allow admins or other trusted users to "lock" discussions (i.e. "close" them) to prevent further commenting, and locked discussions would not appear on the main page either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

1 participant