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 Should we use the Article type for bug reports?
Parent
Should we use the Article type for bug reports?
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 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.
-
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 ↩
-
What would "answering a bug report" even mean in this context? ↩
-
I guess bug reports aren't really "articles" either, but they are "posts that don't have an answer," so it still fits better. ↩
Post
Nah.
Posting them as questions allows for a more detailed explanation than "fixed" if there's a reason to do so - such as an especially interesting bug, or someone taking the opportunity to explain how certain bits of the system work.
Plus, the people who fix the bugs then get the opportunity to increase their imaginary internet points. ;)
0 comment threads