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

66%
+4 −1
Q&A Let's revamp our status tags

One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [s...

4 answers  ·  posted 3y ago by Mithical‭  ·  last activity 3y ago by Olin Lathrop‭

Question discussion tags
#3: Post edited by user avatar Mithical‭ · 2021-04-25T18:52:24Z (over 3 years ago)
  • One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [status-planned]. The tags are marked in red like other moderator-only tags.
  • But... maybe we can do this a little differently?
  • I'd like to knock off the "status-" from the beginning of the tags, and possibly re-color them to differentiate them from other moderator tags.
  • Including the "status" and changing the color would make it clearer, I think, that this has received Official Attention™ and help it stand out. I'm thinking purple, but that's just me. (This would also, admittedly, help us differentiate ourselves from Somewhere Else - there's no reason to keep the existing system because that's what they're using.)
  • As for the status tags, I'd like to propose the following tags and the way they should be used:
  • * [declined]
  • This should be pretty obvious. This bug or feature request has been declined by the team, and won't be fixed or implemented for whatever reason. (This would include the current [status-bydesign]; it's declining the bug report because it's working as designed.)
  • * [planned]
  • This would indicate that something is on our roadmap; this feature is either actively in the works or it's something that we want to do in the relatively near future. In other words, something that we're actively thinking about or will be fixed / implemented as soon as is realistic.
  • * [deferred]
  • A new status tag (for us), this would be something that we would like to get to at some point in the future, but it's not on our roadmap and isn't something we're likely to focus on in the near future. We'd like to consider this at some point in the future, but no promises and we can't consider it right now.
  • * [completed]
  • Again, should be fairly obvious here - this was done and dusted.
  • ----
  • So... thoughts? These are my personal thoughts and suggestions as a regular user, not as a staff member, and I haven't run this past any of the other team members. I'd be interested in hearing what everyone has to say on any part of these suggestions.
  • One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [status-planned]. The tags are marked in red like other moderator-only tags.
  • But... maybe we can do this a little differently?
  • I'd like to knock off the "status-" from the beginning of the tags, and possibly re-color them to differentiate them from other moderator tags.
  • Removing the "status" and changing the color would make it clearer, I think, that this has received Official Attention™ and help it stand out. I'm thinking purple, but that's just me. (This would also, admittedly, help us differentiate ourselves from Somewhere Else - there's no reason to keep the existing system because that's what they're using.)
  • As for the status tags, I'd like to propose the following tags and the way they should be used:
  • * [declined]
  • This should be pretty obvious. This bug or feature request has been declined by the team, and won't be fixed or implemented for whatever reason. (This would include the current [status-bydesign]; it's declining the bug report because it's working as designed.)
  • * [planned]
  • This would indicate that something is on our roadmap; this feature is either actively in the works or it's something that we want to do in the relatively near future. In other words, something that we're actively thinking about or will be fixed / implemented as soon as is realistic.
  • * [deferred]
  • A new status tag (for us), this would be something that we would like to get to at some point in the future, but it's not on our roadmap and isn't something we're likely to focus on in the near future. We'd like to consider this at some point in the future, but no promises and we can't consider it right now.
  • * [completed]
  • Again, should be fairly obvious here - this was done and dusted.
  • ----
  • So... thoughts? These are my personal thoughts and suggestions as a regular user, not as a staff member, and I haven't run this past any of the other team members. I'd be interested in hearing what everyone has to say on any part of these suggestions.
#2: Post edited by user avatar Mithical‭ · 2021-04-25T18:11:16Z (over 3 years ago)
  • One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [status-planned]. The tags are marked in red like other moderator-only tags.
  • But... maybe we can do this a little differently?
  • I'd like to knock off the "status-" from the beginning of the tags, and possibly re-color them to differentiate them from other moderator tags.
  • Including the "status" and changing the color would make it clearer, I think, that this has received Official Attention™ and help it stand out. I'm thinking purple, but that's just me. (This would also, admittedly, help us differentiate ourselves from Somewhere Else - there's no reason to keep the existing system because that's what they're using.)
  • As for the status tags, I'd like to propose the following tags and the way they should be used:
  • * [declined]
  • This should be pretty obvious. This bug or feature request has been declined by the team, and won't be fixed or implemented for whatever reason.
  • * [planned]
  • This would indicate that something is on our roadmap; this feature is either actively in the works or it's something that we want to do in the relatively near future. In other words, something that we're actively thinking about or will be fixed / implemented as soon as is realistic.
  • * [deferred]
  • A new status tag (for us), this would be something that we would like to get to at some point in the future, but it's not on our roadmap and isn't something we're likely to focus on in the near future. We'd like to consider this at some point in the future, but no promises and we can't consider it right now.
  • * [completed]
  • Again, should be fairly obvious here - this was done and dusted.
  • ----
  • So... thoughts? These are my personal thoughts and suggestions as a regular user, not as a staff member, and I haven't run this past any of the other team members. I'd be interested in hearing what everyone has to say on any part of these suggestions.
  • One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [status-planned]. The tags are marked in red like other moderator-only tags.
  • But... maybe we can do this a little differently?
  • I'd like to knock off the "status-" from the beginning of the tags, and possibly re-color them to differentiate them from other moderator tags.
  • Including the "status" and changing the color would make it clearer, I think, that this has received Official Attention™ and help it stand out. I'm thinking purple, but that's just me. (This would also, admittedly, help us differentiate ourselves from Somewhere Else - there's no reason to keep the existing system because that's what they're using.)
  • As for the status tags, I'd like to propose the following tags and the way they should be used:
  • * [declined]
  • This should be pretty obvious. This bug or feature request has been declined by the team, and won't be fixed or implemented for whatever reason. (This would include the current [status-bydesign]; it's declining the bug report because it's working as designed.)
  • * [planned]
  • This would indicate that something is on our roadmap; this feature is either actively in the works or it's something that we want to do in the relatively near future. In other words, something that we're actively thinking about or will be fixed / implemented as soon as is realistic.
  • * [deferred]
  • A new status tag (for us), this would be something that we would like to get to at some point in the future, but it's not on our roadmap and isn't something we're likely to focus on in the near future. We'd like to consider this at some point in the future, but no promises and we can't consider it right now.
  • * [completed]
  • Again, should be fairly obvious here - this was done and dusted.
  • ----
  • So... thoughts? These are my personal thoughts and suggestions as a regular user, not as a staff member, and I haven't run this past any of the other team members. I'd be interested in hearing what everyone has to say on any part of these suggestions.
#1: Initial revision by user avatar Mithical‭ · 2021-04-25T17:54:08Z (over 3 years ago)
Let's revamp our status tags
One of our holdovers from Somewhere Else is the way we mark bugs and feature requests with status tags - including [status-completed], [status-declined], [status-bydesign], and we've got our own [status-planned]. The tags are marked in red like other moderator-only tags.

But... maybe we can do this a little differently?

I'd like to knock off the "status-" from the beginning of the tags, and possibly re-color them to differentiate them from other moderator tags.

Including the "status" and changing the color would make it clearer, I think, that this has received Official Attention™ and help it stand out. I'm thinking purple, but that's just me. (This would also, admittedly, help us differentiate ourselves from Somewhere Else - there's no reason to keep the existing system because that's what they're using.)

As for the status tags, I'd like to propose the following tags and the way they should be used:

* [declined]

  This should be pretty obvious. This bug or feature request has been declined by the team, and won't be fixed or implemented for whatever reason.

* [planned]

  This would indicate that something is on our roadmap; this feature is either actively in the works or it's something that we want to do in the relatively near future. In other words, something that we're actively thinking about or will be fixed / implemented as soon as is realistic.

* [deferred]

  A new status tag (for us), this would be something that we would like to get to at some point in the future, but it's not on our roadmap and isn't something we're likely to focus on in the near future. We'd like to consider this at some point in the future, but no promises and we can't consider it right now.

* [completed]

  Again, should be fairly obvious here - this was done and dusted.

----

So... thoughts? These are my personal thoughts and suggestions as a regular user, not as a staff member, and I haven't run this past any of the other team members. I'd be interested in hearing what everyone has to say on any part of these suggestions.