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.
How do I "answer" a feature request or a bug report?
Given that a feature request or a bug report is more of a call-to-action to the developers rather than a question seeking an "answer," I am confused as to what an answer to a feature request or bug report would look like.
What are the guidelines for "answering" a feature request or bug report in a way that the answer will be well-received?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
In addition to what Monica wrote, yes, a bug report or a feature request is indeed a "call-to-action to the developers", and as such can only really be answered by the developers.
Let me introduce you to the developers of the network: You.
The entire platform is open-source and volunteer-developed. Any community member who has the time, skills, and desire can contribute directly to the codebase - fixing bugs, implementing feature requests, reviewing other people's pull requests... Unlike closed-source projects, you don't necessarily need one of the "official" developers of the project to handle something. Anyone can fix the issue in the code, and then you just need the Codidact Team to take care of deploying it to the live site.
0 comment threads
For bugs, you can use answers to add more information if you have it, for example if you've seen the reported problem under different circumstances or if you have seen something work that is reported as a bug. Most of the time, as you said, a bug report is "answered" by a status-complete tag after a delay.
For feature requests, answers can offer counter-suggestions, elaborations, or design or implementation approaches. A feature, when implemented, doesn't always match the original request; feedback from the community is important in working out how things should behave and in identifying edge cases that need to be considered.
0 comment threads
0 comment threads