Generic robotic controllers to accompany ros2_control
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 65%
Response Time: 2d
First Timer Success: 80%
ros-controls/ros2_controllers has a recorded first-timer success rate of 80.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ros-controls/ros2_controllers respond to incoming external pull requests in approximately 49.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 57.0 places ros-controls/ros2_controllers in the A tier.
The external contributor pull request merge rate for ros-controls/ros2_controllers is 65.3%, based on public PR activity from non-core contributors.
ros-controls/ros2_controllers currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (70% critical review signals). Ensure PRs strictly follow guidelines before requesting review in ros-controls/ros2_controllers.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/ros-controls/ros2_controllers?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~32 hours (82% approval). Large PRs (>500 lines) take ~239 hours (29% approval). Keep your diff compact for rapid review.
Background There are logic flaws here: ros2_controllers/mecanum_drive_controller/src/mecanum_drive_controller.cpp Lines 559 to 562 in 5a52e84 const bool value_set_error = command_interfaces_[FRONT_LEFT].set_value(0.0) && command_interfaces_[FRONT_RIGHT].set_value(0.0) && command_interfaces_[REAR_RIGHT].set_value(0.0) && command_interfaces_[REAR_LEFT].set_value(0.0); It one set_value() fails, the other setters won't be called at all. Still, if one fails the robot would move weirdly and possibly pose a safety risk -> we should use a blocking version of set_value() Chang it to || logic set max_tries to -1 (it will try forever): set_value(0.0, -1) Fix also these parts
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to ros-controls/ros2_controllers, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of ros-controls/ros2_controllers acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.3% were successfully merged into the primary branch.
ros-controls/ros2_controllers has a recorded first-timer success rate of 80.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 57.0 places ros-controls/ros2_controllers in the Welcoming tier.
The external pull request merge rate is 65.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ros-controls/ros2_controllers currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ros-controls/ros2_controllers are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.