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
I've recently been looking through the [bug] tag, and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation ther...
#3: Post edited
by
Moshi
·
2020-09-10T03:04:03Z (over 3 years ago)
oops left a half written edit in there
- I've recently been looking through the [[bug] tag](https://meta.codidact.com/categories/3/tags/394), and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation thereof). Even that one answer is unnecessary anyway since the status tags easily show whether the bug has been fixed.
- Therefore, I've been thinking that we should just use the Article type for bugs,[^1] since there really isn't a point to answering a bug report.[^2] I believe that tools should be used for what they're developed for: the Q&A type of post should be for questions that have answers, which bug posts are not.[^3]
Since apparently post types are determined by catagory,- I'm aware that this would be a pretty big change for not much benefit, but I thought I'd throw it out here for consideration.
- [^1]: I'm not saying we need to change the old bug reports (since I don't think it's even possible), just use it for new ones
- [^2]: What would "answering a bug report" even *mean* in this context?
- [^3]: I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better.
- I've recently been looking through the [[bug] tag](https://meta.codidact.com/categories/3/tags/394), and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation thereof). Even that one answer is unnecessary anyway since the status tags easily show whether the bug has been fixed.
- Therefore, I've been thinking that we should just use the Article type for bugs,[^1] since there really isn't a point to answering a bug report.[^2] I believe that tools should be used for what they're developed for: the Q&A type of post should be for questions that have answers, which bug posts are not.[^3]
- I'm aware that this would be a pretty big change for not much benefit, but I thought I'd throw it out here for consideration.
- [^1]: I'm not saying we need to change the old bug reports (since I don't think it's even possible), just use it for new ones
- [^2]: What would "answering a bug report" even *mean* in this context?
- [^3]: I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better.
#2: Post edited
by
Moshi
·
2020-09-10T03:03:23Z (over 3 years ago)
Got rid of the salty footnote
- I've recently been looking through the [[bug] tag](https://meta.codidact.com/categories/3/tags/394), and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation thereof). Even that one answer is unnecessary anyway since the status tags easily show whether the bug has been fixed.
- Therefore, I've been thinking that we should just use the Article type for bugs,[^1] since there really isn't a point to answering a bug report.[^2] I believe that tools should be used for what they're developed for: the Q&A type of post should be for questions that have answers, which bug posts are not.[^3]
I'm aware that this would be a pretty big change for not much benefit, but I thought I'd throw it out here for consideration.[^4]- [^1]: I'm not saying we need to change the old bug reports (since I don't think it's even possible), just use it for new ones
- [^2]: What would "answering a bug report" even *mean* in this context?
[^3]: I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better.[^4]: Anyway, awaiting incoming downvotes because "don't fix what ain't broke." Thankfully, *I don't care.*
- I've recently been looking through the [[bug] tag](https://meta.codidact.com/categories/3/tags/394), and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation thereof). Even that one answer is unnecessary anyway since the status tags easily show whether the bug has been fixed.
- Therefore, I've been thinking that we should just use the Article type for bugs,[^1] since there really isn't a point to answering a bug report.[^2] I believe that tools should be used for what they're developed for: the Q&A type of post should be for questions that have answers, which bug posts are not.[^3]
- Since apparently post types are determined by catagory,
- I'm aware that this would be a pretty big change for not much benefit, but I thought I'd throw it out here for consideration.
- [^1]: I'm not saying we need to change the old bug reports (since I don't think it's even possible), just use it for new ones
- [^2]: What would "answering a bug report" even *mean* in this context?
- [^3]: I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better.
#1: Initial revision
by
Moshi
·
2020-09-10T02:20:52Z (over 3 years ago)
Should we use the Article type for bug reports?
I've recently been looking through the [[bug] tag](https://meta.codidact.com/categories/3/tags/394), and one thing stood out to me. Every bug post either has no answers, or one answer that just says, "The bug has been fixed" (or some variation thereof). Even that one answer is unnecessary anyway since the status tags easily show whether the bug has been fixed. Therefore, I've been thinking that we should just use the Article type for bugs,[^1] since there really isn't a point to answering a bug report.[^2] I believe that tools should be used for what they're developed for: the Q&A type of post should be for questions that have answers, which bug posts are not.[^3] I'm aware that this would be a pretty big change for not much benefit, but I thought I'd throw it out here for consideration.[^4] [^1]: I'm not saying we need to change the old bug reports (since I don't think it's even possible), just use it for new ones [^2]: What would "answering a bug report" even *mean* in this context? [^3]: I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better. [^4]: Anyway, awaiting incoming downvotes because "don't fix what ain't broke." Thankfully, *I don't care.*