Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Comments on Could we have a "Close as outdated" close reason?

Parent

Could we have a "Close as outdated" close reason?

+3
−1

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>.)"

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (2 comments)
Post
+0
−0

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.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

superseded != completed (1 comment)
superseded != completed
Monica Cellio‭ wrote about 1 year ago

The close reason we have now (just here on Meta) is "outdated or superseded", and using the reason requires a link. Not everything that is outdated is completed; sometimes a proposal led to a follow-on, like the last link in the question. Status tags wouldn't fit there; the post is neither completed nor declined, but rather, continued elsewhere.

As far as I know, this close reason isn't used on any "main" site, for the reasons you mention. It's possible that a resource collection or article might want to mark things as superseded, but I don't think it's come up yet.