Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Could we have a "Close as outdated" close reason?
A sort of a solution to this problem, but would also apply to posts such as moderator elections, one-off proposals (though status-complete also works), and just generally posts which at some point had relevance but no longer, (such as some questions about comments once the new comment system is implemented).
I propose adding a close reason, "Closed as outdated", with the option to link to a more relevant post such as in the case of the Panel discussion, or a link to the change which made the question obsolete.
A proposed close text might be, "This post is no longer relevant due to <insert reason here>. (optional: For more information, see <insert link here>.)"
2 answers
Sure. I've added the reason here on Meta; we'll see how it goes. If it turns out to be more widely useful we can look at getting it added to community seeds and existing communities.
I generally don't think this is a good idea. As you note, status-completed tags work fine for noting that a Meta process has run its course. If such a process has run its course - why not use the same post for post-mortem discussion?
For main-space questions, if a question is about a problem that should be "obsolete", that doesn't mean people will stop having to worry about it. Especially in technical fields: legacy systems are all over the place. The financial sector is still heavily dependent on COBOL.
If anything needs to be added, I would suggest (if only for symmetry) allowing for the addition of "outdated" reactions on question posts. Which is to say, mark the post with all the information you describe, but don't close it.
1 comment thread