Integration between ROS (1 and 2) and Gazebo simulation
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 33%
Response Time: 2d
First Timer Success: -
gazebosim/ros_gz has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gazebosim/ros_gz respond to incoming external pull requests in approximately 38.5 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 46.4 places gazebosim/ros_gz in the B tier.
The external contributor pull request merge rate for gazebosim/ros_gz is 33.3%, based on public PR activity from non-core contributors.
gazebosim/ros_gz currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in gazebosim/ros_gz welcoming community pull requests and bug fixes.
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/gazebosim/ros_gz?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (42% approval). Large PRs (>500 lines) take ~185 hours (15% approval). Keep your diff compact for rapid review.
Environment ROS 2: Humble Gazebo: Harmonic OS: Ubuntu 22.04 ros_gz_bridge version: ros_gzharmonic_bridge Description I'm trying to bridge Gazebo's /world/default/set_pose service to ROS 2 using ros_gz_bridge, so that I can reset robot states for reinforcement learning. Previously, with ROS2 Humble + Gazebo Fortress, the following command worked and the service appeared in ros2 service list: ros2 run ros_gz_bridge parameter_bridge /world/default/set_pose@ros_gz_interfaces/srv/SetEntityPose Now, with Gazebo Harmonic, I understand that the service types need to be fully specified. I tried the following command: ros2 run ros_gz_bridge parameter_bridge /world/default/set_pose@ros_gz_interfaces/srv/[email protected]@gz.msgs.Boolean However, after running this, /world/default/set_pose still does not appear in ros2 service list. No error message is printed in the terminal. Additional context: I confirmed that /world/default/set_pose is available in Gazebo via gz service -l.
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 gazebosim/ros_gz, 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 gazebosim/ros_gz acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
gazebosim/ros_gz has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 46.4 places gazebosim/ros_gz in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gazebosim/ros_gz 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 gazebosim/ros_gz 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.