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 Should we use the Article type for bug reports?

Parent

Should we use the Article type for bug reports?

+2
−4

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.

  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.

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?

0 comment threads

Post
+3
−0

I've sometimes seen bug reports be answered with workaround while awaiting a fix. I think I've seen that here on Codidact (though I haven't gone looking for examples). I know I saw it sometimes on Some Other site. I don't know how important it is, but it's something we would lose if we made this change.

We can't currently tie post types to tags, so this would be a convention of using the article post type when reporting bugs but not something we could enforce through the system. This means there'll be a learning curve and some mis-fires.

Available post types are tied to the category. If we kept bug reports here in the main Q&A category and wanted people to use articles for them, then asking a question here would require explicitly choosing a post type (question or article) each time. (When there's only one type of top-level post the software doesn't ask because you only have one choice.) This could be mitigated by creating a separate category for bug reports; I don't know if that segregation would be a good thing or a bad thing.

We probably need a better approach to bug reports than what we have now, but I don't know what that is. Suggestions welcome!

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 (5 comments)
General comments
Moshi‭ wrote about 4 years ago

I personally think workarounds should just be edited into the post itself, or left as comments.

Moshi‭ wrote about 4 years ago

To be entirely honest, I wish people would just post bug reports on github as a new issue so it'd all be gathered in one place, but I can't expect everyone to have a github account.

Moshi‭ wrote about 4 years ago

Also, I actually think that separating bug reports into it's own category would be immensely helpful - those reports tend to get buried beneath all the new stuff, since they are rarely updated, and it'll be much easier to find previous reports once search by catagory is implemented.

ShowMeBillyJo‭ wrote about 4 years ago

@Moshi Agree re. GitHub; it's the ideal, but not feasible to expect many user-reported bug reports to start and end there. A separate category with some guidance for posting a good bug report would be a good second option, but there's still the possibility of folks reporting in Q&A. There'd need to be a way to migrate posts from one category+type to another.

msh210‭ wrote about 4 years ago

Re workarounds: I think that's sufficient reason to leave bug reports as "questions".