# Prioritizing ROS Issues: An experiment

**URL:** <https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801>\
**Category:** ROS General\
**Created:** [February 14, 2023, 7:14pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801 "2023-02-14T19:14:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DLu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/dlu/32/19014_2.png) [@DLu](https://discourse.openrobotics.org/u/DLu)\
**Post date:** [February 14, 2023, 7:14pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/1 "2023-02-14T19:14:44Z")

</div>

**tl; dr: I made a [ROS Feedback Portal](http://ros-feedback.metrorobots.com:3000/) using [Fider](https://fider.io/) for voting on issues in the greater ROS ecosystem.**

 ![rosfeedback](https://us1.discourse-cdn.com/flex022/uploads/ros/original/3X/3/5/35e18e20703bb51d49439022c627f701c025b62b.png)

_Disclaimer: This is an experimental prototype with no guaranteed consequences. The highest voted issue will not necessarily receive development time. I’m an individual developer who is trying out an idea independently._

Problem: Its hard to know what the biggest pain points are across the ROS ecosystem, especially when it is spread across multiple GitHub organizations and non-Github places. While you can comment and emoji-react to issues on GitHub and then sort by most comments / [most emoji](https://github.com/ros2/ros2_documentation/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc), its not the most straightforward approach. Case and point: [This thread](http://discourse.ros.org/t/improving-the-developer-experience/29774)

Possible solution: Fider is a “feedback portal for feature requests and suggestions” for giving “customers” a way to express what they need.

The idea is for the community to submit issues that they’d like to see get more traction, and the community can upvote them as a way to say “this is also a problem for me right now”. And then the community’s needs that intrinsically are affecting the most people rise to the top.

(At one point, this was my plan for helping steer the ROS 2 TSC to meet the communities needs.)

(Apologies for the URL. I’d blame Docker, but its really an Apache problem that I’m too lazy to research.)

---

<div class="post-metadata">

**Author:** ![peci1](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/peci1/32/10145_2.png) [@peci1](https://discourse.openrobotics.org/u/peci1)\
**Post date:** [February 14, 2023, 7:33pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/2 "2023-02-14T19:33:06Z")

</div>

Awesome! Can I add tags, or is that allowed only for you, @DLu ?

---

<div class="post-metadata">

**Author:** ![DLu](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/dlu/32/19014_2.png) [@DLu](https://discourse.openrobotics.org/u/DLu)\
**Post date:** [February 14, 2023, 7:36pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/3 "2023-02-14T19:36:01Z")

</div>

Right now I’m the only administrator. I bumped you up to Collaborator, which might help. I’m open to suggestions for new tags.

---

<div class="post-metadata">

**Author:** ![peci1](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/peci1/32/10145_2.png) [@peci1](https://discourse.openrobotics.org/u/peci1)\
**Post date:** [February 14, 2023, 7:44pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/4 "2023-02-14T19:44:49Z")

</div>

Thanks. What about tags `core`, `tf`, `control`, `navigation`, `sensor processing`?

---

<div class="post-metadata">

**Author:** ![Achllle](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/achllle/32/4397_2.png) [@Achllle](https://discourse.openrobotics.org/u/Achllle)\
**Post date:** [February 16, 2023, 8:12pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/5 "2023-02-16T20:12:23Z")

</div>

I think this is exactly what we need! Would love to see this incorporated on various landing pages.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/ros/original/3X/b/6/b607ee3cc8e908b1b613bd74a683d749fea635a1.svg) [@system](https://discourse.openrobotics.org/u/system)\
**Post date:** [March 18, 2023, 8:13pm UTC](https://discourse.openrobotics.org/t/prioritizing-ros-issues-an-experiment/29801/6 "2023-03-18T20:13:09Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.