Learn Robotics with JdeRobot
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 64%
Response Time: 13h
First Timer Success: 50%
JdeRobot/RoboticsAcademy has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in JdeRobot/RoboticsAcademy respond to incoming external pull requests in approximately 12.6 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 68.6 places JdeRobot/RoboticsAcademy in the A tier.
The external contributor pull request merge rate for JdeRobot/RoboticsAcademy is 64.1%, based on public PR activity from non-core contributors.
JdeRobot/RoboticsAcademy currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in JdeRobot/RoboticsAcademy 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/JdeRobot/RoboticsAcademy?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 09:00 UTC (09: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 ~8 hours (80% approval). Large PRs (>500 lines) take ~60 hours (29% approval). Keep your diff compact for rapid review.
We would like to check that the Service Robotics course exercises work well when they are solved in direct ROS 2 mode, meaning that you write your own ROS 2 node instead of relying only on the HAL API. We want to confirm this both in Python and in C++, and we would really appreciate help from the community. The exercises we would like tested are Localized Vacuum Cleaner Autoparking Amazon Warehouse Rescue People Visual Marker Localization Laser Mapping What we are asking is simple. Pick any of these exercises, try to solve it and run it in direct ROS 2 mode using Python and also C++, and tell us how it went. If everything works we would love to hear it, and if something does not work we want to know about it. We are especially interested in three kinds of problems Anything in the documentation that is missing, outdated or unclear when you try to solve the exercise in direct ROS 2 Any import in Python or any dependency in C++ that you needed but were not able to add, or that failed t
We would like to check that the Mobile Robotics course exercises work well when they are solved in direct ROS 2 mode, meaning that you write your own ROS 2 node instead of relying only on the HAL API. We want to confirm this both in Python and in C++, and we would really appreciate help from the community. The exercises we would like tested are Basic Vacuum Cleaner Follow Line Obstacle Avoidance Global Navigation Laser Mapping Montecarlo Laser Localization What we are asking is simple. Pick any of these exercises, try to solve it and run it in direct ROS 2 mode using Python and also C++, and tell us how it went. If everything works we would love to hear it, and if something does not work we want to know about it. We are especially interested in three kinds of problems Anything in the documentation that is missing, outdated or unclear when you try to solve the exercise in direct ROS 2 Any import in Python or any dependency in C++ that you needed but were not able to add, or that fail
This is only for the new universe that has a 3d lidar, not the old one with 3 lasers. The documentation available is for the 3 lasers exercises, not the 3d lidar one. Share here any issues, not solutions, related to this exercises. Do not comment anything else other than that. This issue is not meant to be assigned to a single person, as its purpose is that multiple people test it.
Share here any issues, not solutions, related to this exercises. Do not comment anything else other than that. This issue is not meant to be assigned to a single person, as its purpose is that multiple people test it.
Share here any issues, not solutions, related to this exercises. Do not comment anything else other than that. This issue is not meant to be assigned to a single person, as its purpose is that multiple people test it.
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 JdeRobot/RoboticsAcademy, 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 JdeRobot/RoboticsAcademy acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.1% were successfully merged into the primary branch.
JdeRobot/RoboticsAcademy has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 hours. 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 68.6 places JdeRobot/RoboticsAcademy in the Welcoming tier.
The external pull request merge rate is 64.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, JdeRobot/RoboticsAcademy currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for JdeRobot/RoboticsAcademy 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.