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.

Post History

71%
+3 −0
Q&A Let's revamp our status tags

I agree that distinguishing these kinds of responses from other moderator-only tags would be helpful, and that we don't need to keep doing what we started doing early on when we needed something. ...

posted 3y ago by Monica Cellio‭  ·  edited 3y ago by Monica Cellio‭

Answer
#2: Post edited by user avatar Monica Cellio‭ · 2021-04-26T00:05:16Z (almost 3 years ago)
Oops, I meant to cast that as more of a question. Thanks Moshi.
  • I agree that distinguishing these kinds of responses from other moderator-only tags would be helpful, and that we don't need to keep doing what we started doing early on when we needed *something*.
  • The "status-" is part of the name to avoid having only one type of "encoding"; somebody who can't see the colors can still tell the difference. We'll need to make sure that whatever we do works for screen readers. (Is there a way to add metadata that readers can use?)
  • On some community metas, moderators use status tags to indicate community, rather than platform, resolutions. For example, a community might have a meta post about changing help text or close reasons or some configuration. This means that either we need different tags or moderators need to be able to use these tags too. I don't know if that's confusing.
  • Scope creep: For issues that end up in tickets on GitHub (many of them, if they aren't solved quickly and aren't user-support issues), it'd be nice to have a canonical place to add that link on the meta post, instead of having to use comments. This way community members could track the ticket's activity. Since only moderators or admins can add these tags, we could either add the field in the question edit interface for them all the time (in categories that use these tags only) or prompt for it if a "status" tag is used. It shouldn't be required, because there won't always be a ticket (at all, or yet).
  • I agree that distinguishing these kinds of responses from other moderator-only tags would be helpful, and that we don't need to keep doing what we started doing early on when we needed *something*.
  • The "status-" is part of the name to avoid having only one type of "encoding"; somebody who can't see the colors can still tell the difference. We'll need to make sure that whatever we do works for screen readers. (Is there a way to add metadata that readers can use?) Are the names alone (and the context of a meta question) enough for people who can't see the colors, or do we need to have some sort of prefix (needn't be "status-")?
  • On some community metas, moderators use status tags to indicate community, rather than platform, resolutions. For example, a community might have a meta post about changing help text or close reasons or some configuration. This means that either we need different tags or moderators need to be able to use these tags too. I don't know if that's confusing.
  • Scope creep: For issues that end up in tickets on GitHub (many of them, if they aren't solved quickly and aren't user-support issues), it'd be nice to have a canonical place to add that link on the meta post, instead of having to use comments. This way community members could track the ticket's activity. Since only moderators or admins can add these tags, we could either add the field in the question edit interface for them all the time (in categories that use these tags only) or prompt for it if a "status" tag is used. It shouldn't be required, because there won't always be a ticket (at all, or yet).
#1: Initial revision by user avatar Monica Cellio‭ · 2021-04-25T18:55:57Z (almost 3 years ago)
I agree that distinguishing these kinds of responses from other moderator-only tags would be helpful, and that we don't need to keep doing what we started doing early on when we needed *something*.  

The "status-" is part of the name to avoid having only one type of "encoding"; somebody who can't see the colors can still tell the difference.  We'll need to make sure that whatever we do works for screen readers.  (Is there a way to add metadata that readers can use?)

On some community metas, moderators use status tags to indicate community, rather than platform, resolutions.  For example, a community might have a meta post about changing help text or close reasons or some configuration.  This means that either we need different tags or moderators need to be able to use these tags too.  I don't know if that's confusing.

Scope creep: For issues that end up in tickets on GitHub (many of them, if they aren't solved quickly and aren't user-support issues), it'd be nice to have a canonical place to add that link on the meta post, instead of having to use comments.  This way community members could track the ticket's activity.  Since only moderators or admins can add these tags, we could either add the field in the question edit interface for them all the time (in categories that use these tags only) or prompt for it if a "status" tag is used.  It shouldn't be required, because there won't always be a ticket (at all, or yet).