Pointing users/posters to the correct support channel has been a practice for a long time, and it makes complete sense. As a maintainer I also don’t like issue trackers being used for how-should-this-be-configured questions or anything else which is not actually an issue. And vice-versa, there are plenty of examples here on ROS Discourse where actual issues are posted which should’ve been posted on a GH issue tracker.
Having written that, I believe we could perhaps improve a bit here.
It’s not uncommon for users posting on ROS Discourse, to be redirected to ROS Answers, posting there and then never receiving a response.
I can’t be sure, but I have the impression this is especially happening to ROS 2 related questions (here on Discourse but also on github.com/ros2
repositories).
The keep-everything-on-topic aspect of “please post this on ROS Answers” is and we should keep doing that.
Redirecting a support question to ROS Answers and then not following up there is something we should probably improve upon.
The number of topic experts on ROS Answers is very limited, so adding more posts to the already growing number of unanswered questions will not help keep ROS Answers the valuable resource it has been.
<call_to_action>
So if you redirect someone and already happen to know the answer (but don’t want to respond to the original, off-topic post) please follow up on ROS Answers. This is especially true for ROS 2 topics, as those tend to be technical, often ask about specific details of the implementation or design and really need an answer by someone in-the-know.
</call_to_action>
If we keep redirecting but then not answering, it looks like we’re trying to get rid of people, which I believe is not the goal here.