JAMQ (Just another meta question):

On the former SQLA site, there have been only a few questions that were closed.

As Justin has obviously cleaned-up his bunch of older questions by closing them (as "answered and accepted") - is this something that should be done generally when questions have an accepted answer?

Or is this irritating as the questions might still be of interest for other readers?

What do you think?


Note, I'm not refering to other reasons to close questions (offensive, off-topic and the like). I do not know whether there have ever been such cases but then closing would be appropriate ...

This question is marked "community wiki".

asked 29 Mar '11, 07:30

Volker%20Barth's gravatar image

Volker Barth
30.3k301454660
accept rate: 32%

wikified 29 Mar '11, 07:32

My theory was (and this was really just an experiment) to close the questions to show that they were complete (as question and answers) and to encourage people who had further related questions to start their own, rather than as sometimes happens on the old groups, to tack on a new question to something that maybe several years out of date. The questions still remain searchable etc, for people looking for information.

Very interested to know what people think the policy should be.

(29 Mar '11, 07:48) Justin Willey
Replies hidden
2

That seem to be senseful reasons (which is not unexpected...) and an intersting experiment. - Apparently the NNTP groups do miss a "closed" action much more:)

For the "aging" of questions, I hope the version-related tags should help to filter out topics for older versions. Though I guess it will take a long time until that aging happens - compared to the much older NNTP groups.

What I do not like about the closing is that it put all these questions to the top of the questions list. That is somewhat confusing - as is when lots of questions are re-tagged.

(29 Mar '11, 07:57) Volker Barth
1

I think this business of what should promote a question back to the top of the list is interesting. I suggest that administrative actions - eg closing, re-tagging etc should not.

(29 Mar '11, 08:25) Justin Willey

In my opinion (note that this is only my opinion and not necessarily that of Sybase), most questions should be left open, even after an answer has been accepted. In some cases, the answer could change in future versions and we want to make it easy to modify the answer.

At least one of the questions Justin closed is answered by "This is a bug and it's fixed in version XXX", and that answer will not change. If someone else sees the same problem at some point in the future (and has the bug fix applied), which would we rather them do:

  1. add a comment to the existing question saying "I'm seeing this behaviour but I have the bug fix" or
  2. ask a brand new question?

I'm not sure of the answer, but we're not likely to be getting StackOverflow numbers here, so it's not really going to come up all that often. Also, once we fix a bug, it never comes back so it's all moot anyway. :-)

Questions that are sqla-specific can be closed.

permanent link

answered 29 Mar '11, 08:12

Graeme%20Perrow's gravatar image

Graeme Perrow
8.5k371109
accept rate: 52%

1

I agree with Graeme... I don't care if questions stay open, and the very act of closing a question draws fresh (and unwarranted) attention to the question IMO.

(30 Mar '11, 08:08) Breck Carter
Replies hidden

Might that though be an argument for admin activities not promoting questions rather than not closing questions? Not sure.

(30 Mar '11, 08:11) Justin Willey
2

I agree that one should be able to influence whether an edit operation puts the question on top of the "active" list.

As long as such a feature is not available, I think closing questions seems not too necessary. And generally, I guess there's a much greater need to mark questions as accepted... (Not for questions asked by the members of this discussion, methinks.)

(30 Mar '11, 08:29) Volker Barth
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×164

question asked: 29 Mar '11, 07:30

question was seen: 567 times

last updated: 30 Mar '11, 08:29