Generic and simple controls framework for ROS 2
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 61%
Response Time: 2d
First Timer Success: 42%
ros-controls/ros2_control has a recorded first-timer success rate of 42.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ros-controls/ros2_control respond to incoming external pull requests in approximately 54.9 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 62.7 places ros-controls/ros2_control in the A tier.
The external contributor pull request merge rate for ros-controls/ros2_control is 61.0%, based on public PR activity from non-core contributors.
ros-controls/ros2_control currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in ros-controls/ros2_control. Maintains strict focus on technical quality and test standards.
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_control?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (76% approval). Large PRs (>500 lines) take ~263 hours (27% approval). Keep your diff compact for rapid review.
The docstring from the init method from JointLimiterInterface is a bit inaccurate. In particular: /** * Wrapper init method that accepts the joint names and their limits directly */ ... virtual bool init( const std::vector<std::string> & joint_names, const std::vector<joint_limits::JointLimits> & joint_limits, const std::vector<joint_limits::SoftJointLimits> & soft_joint_limits, const rclcpp::node_interfaces::NodeParametersInterface::SharedPtr & param_itf, const rclcpp::node_interfaces::NodeLoggingInterface::SharedPtr & logging_itf) .... This overload also takes soft_joint_limits, not just names and limits as mentioned in the docstring. For instance: /** * Wrapper init method that accepts the joint names, their limits directly, and the soft joint limits. */
Is your feature request related to a problem? Please describe. I have an actuator that has a position command interface, as well as position and velocity state interfaces. My robot description looks a bit like this: <joint name="my_joint" type="prismatic"> <limits lower="-10.0" upper="10.0" velocity="0.1" effort="10" /> </joint> <ros2_control name="MockJoint" type="system"> <hardware> <plugin>mock_components/GenericSystem</plugin> </hardware> <joint name="my_joint"> <command_interface name="position" /> <state_interface name="position" /> <state_interface name="velocity" /> </joint> </ros2_control> The controller manager's parameters: controller_manager: ros__parameters: update_rate: 50 enforce_command_limits: true # because I'm using Jazzy I want to enable limiting on the position command, however, this also sets has_velocity_limits (and all the others) to true. Controller manager log: [ros2_control_node-1] [INFO] [controller_manager]: Using Join
• ## Summary ThreadSanitizer reports data races in controller_manager::ControllerManager during concurrent control-cycle updates. Affected Location controller_manager/src/controller_manager.cpp:2241 ControllerManager::RTControllerListWrapper::update_and_get_used_by_rt_list() controller_manager/src/controller_manager.cpp:2186 ControllerManager::update(rclcpp::Time const&, rclcpp::Duration const&) Observed Result ThreadSanitizer reports concurrent writes in both paths. WARNING: ThreadSanitizer: data race (pid=413) Write of size 4 ... #0 ...update_and_get_used_by_rt_list() .../controller_manager.cpp:2241 Previous write of size 4 ...
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_control, 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_control acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.0% were successfully merged into the primary branch.
ros-controls/ros2_control has a recorded first-timer success rate of 42.1%. 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 62.7 places ros-controls/ros2_control in the Welcoming tier.
The external pull request merge rate is 61.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ros-controls/ros2_control currently has 3 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_control 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.