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 Bug Reports category

Parent

Bug Reports category

+4
−6

Meta should have a dedicated category for bug reports, to increase the chance that users will pile onto an existing bug report rather than create new ones.

Even people who can't be bothered to search, are on a platform where searching is painful, or who search ineffectively, might notice a dup report on the first page of a bug category.

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?

1 comment thread

General comments (4 comments)
Post
+3
−0

We do technically have a dedicated bug reports channel on Github.

Rather than making a separate category on Meta, it might make more sense to keep all bug reports relating to the software on Github. Eventually others might self-host Codidact instances, and having a central repository of known issues for developers to be aware of would be preferable to having them simply buried as Meta posts somewhere on the canonical Codidact instance.

The downside to using the Github issues tracker is that some Codidact users may not have or want an account on another site. We could work around this by having a "submit an issue" button on Codidact and automatically posting those issues to the tracker, but that would likely be a hassle for the developers to set up (correct me if I'm wrong).

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 (2 comments)
General comments
manassehkatz‭ wrote over 4 years ago

It is more than just "an account on another site". Some existing users, and I expect many future users, will be relatively non-technical types. They may be experts on photography or cooking but not programmers/developers. As such, posting to Meta will be easy (same as the communities they are using) but Github will be quite foreign. In addition, the Meta Codidact instance, at least at the "bug & development tracking" level (as opposed to policy issues) can function for independent instances

manassehkatz‭ wrote over 4 years ago

as well. If a group of people want to spin up their own site, either to host a "private" group or in order to have policies that differ from ours, they can still come here to post bug reports or feature requests, and then update their own instance from the master instance on Github when changes are implemented.