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 [status-completed] posts bury everything else

Parent

[status-completed] posts bury everything else

+3
−1

At the time of writing, there is a big chunk of (around 15) [status-completed] and [status-declined] posts in the Q&A category feed, burying the open posts.

Since open posts are much more important than completed ones, I think that this situation should be avoided. I suggest either:

  1. Add an option to hide [status-completed] or other related tags from the category feed.
  2. Don't bump posts when adding the [status-completed] or related tags to them.
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 (1 comment)
Post
+1
−0

I would like to offer a third alternative.

Don't make post-bumping edits in bulk.

I don't know the process that led up to those posts being retagged the way they were just now, but I strongly suspect that they didn't all need to be retagged at once.

So, then, the obvious option would be to retag as soon as possible when the correct tag becomes known, whether that's status-completed, status-declined, or unicorn-failure. (Okay, maybe not that last one, even though we did have a genuine unicorn failure some time ago.)

Spreading the edits out over a longer period of time means that other posts don't get buried by ones that are bumped simply because of a moderator tag edit.

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

1 comment thread

General comments (2 comments)
General comments
luap42‭ wrote about 4 years ago

Normally we try to add the tags as soon as they are fixed, but there are two possible exceptional conditions: (1) many easy fixes rolled out at one end. what should be done here else? and (2) adding status tags to older, “forgotten” requests.

Canina‭ wrote about 4 years ago

@luap42 I guess that depends largely on what we want particularly "status-completed" to mean; installed in production or fix ready, tested and will be deployed but might not necessarily be deployed yet? From a user perspective, the former is more approachable; from a developer perspective, the latter is attractive and still carries info to the user. Older, forgotten requests will of course remain a problem but those edits can probably be spaced out over time with no significant downside.