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.

Should bugs and feature requests go to local Metas or Meta.Codidact?

+8
−1

When users of a Codidact site come up with bugs or feature requests that are not specific to that site:

  • Is it preferable that they post to their local Meta or to Meta.Codidact?

  • Is one of these options strictly the correct practice?

  • If not, what are the pros and cons of each?

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (3 comments)

1 answer

+8
−0

If you know that a bug or feature request is broader than just your site, it's better to post it on main meta if you can. (Things known to be specific to one site belong on the per-site meta.) Reporting bugs or requesting features on main meta should mean less duplication compared to reports on (possibly multiple) per-site metas. A post on main meta also has broader visibility, meaning more people are in a position to contribute to the discussion. This extra visibility might, in some cases, get you an answer from another community member (like a workaround for a bug) before a Codidact team member has ever seen it. For feature requests in particular, knowing how other sites would use the requested change (or what obstacles they would face with it) is helpful info we wouldn't get from posts on per-site metas.

But that's a preference, not a requirement. If you (or your users) post it on the per-site meta, either because people don't want to come to main meta or out of lack of awareness, that's fine. We'll see it, and we're not going to get hung up on "you should have posted this over there". Besides, people don't always know what's a per-site configuration issue versus a general issue. If we get duplicate bug reports we'll collapse them at our end.

Where you post doesn't affect response time from the Codidact team. We feed all new meta posts into one bin for processing, along with issues reported on GitHub and things discovered directly by the development team. We're not using any of the metas as issue trackers but, rather, issue feeders. (That said, we do make our best effort to go back to wherever an issue was reported to update status when we resolve it.)

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »