Generic and simple controls framework for ROS 2
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 67%
Response Time: 10d
First Timer Success: 53%
ros-controls/ros2_control has a recorded first-timer success rate of 52.6%. Repositories ranked B 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 229.8 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 47.8 places ros-controls/ros2_control in the B tier.
The external contributor pull request merge rate for ros-controls/ros2_control is 67.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".
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)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
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. */
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 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.0% were successfully merged into the primary branch.
ros-controls/ros2_control has a recorded first-timer success rate of 52.6%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 47.8 places ros-controls/ros2_control in the Solid tier.
The external pull request merge rate is 67.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.