The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I agree with @dornhege's response, that this is probably not a good format for doing feature requests.
I think that having both support questions and feature requests in the same area would end up in chaos.
I think that there are a few channels for feature requests already in existence.
Finally, if you want to get into the long-term planning of ROS, I strongly encourage you to join one of the Planning SIGS for determining the direction of development for Groovy and forward.
| | 2 | No.2 Revision |
I agree with @dornhege's response, that this is probably not a good format for doing feature requests.
I think that having both support questions and feature requests in the same area would end up in chaos.
I think that there are a few channels for feature requests already in existence.
Finally, if you want to get into the long-term planning of ROS, I strongly encourage you to join one of the Planning SIGS for determining the direction of development for Groovy and forward.
| | 3 | No.3 Revision |
I agree with @dornhege's response, that this is probably not a good format for doing feature requests.
I think that having both support questions and feature requests in the same area would end up in chaos.
I think that there are a few channels for feature requests already in existence.
Finally, if you want to get into the long-term planning of ROS, I strongly encourage you to join one of the Planning SIGS for determining the direction of development for Groovy and forward.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
