eclipse-zenoh/zenoh-plugin-ros2dds - Open Source PR Review Scorecard

A Zenoh plug-in for ROS2 with a DDS RMW. See https://discourse.ros.org/t/ros-2-alternative-middleware-report/ for the advantages of using this plugin over other DDS RMW implementations.

C-Rank Grade: C (Moderate) - 28/100

External PR Merge Rate: 18%

Response Time: 4d

First Timer Success: 50%

Frequently Asked Questions

Is eclipse-zenoh/zenoh-plugin-ros2dds welcoming to first-time open-source contributors?

eclipse-zenoh/zenoh-plugin-ros2dds has a recorded first-timer success rate of 50.0%. Repositories ranked C typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in eclipse-zenoh/zenoh-plugin-ros2dds respond to incoming external pull requests in approximately 103.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 28.5 C-Rankâ„¢ score (C Tier) represent?

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 28.5 places eclipse-zenoh/zenoh-plugin-ros2dds in the C tier.

What is the external contributor pull request merge rate for eclipse-zenoh/zenoh-plugin-ros2dds?

The external contributor pull request merge rate for eclipse-zenoh/zenoh-plugin-ros2dds is 18.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in eclipse-zenoh/zenoh-plugin-ros2dds?

eclipse-zenoh/zenoh-plugin-ros2dds does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

eclipse-zenoh
eclipse-zenoh/zenoh-plugin-ros2ddsC•Moderate298
GitHub
Back to Explorer
eclipse-zenoh

eclipse-zenoh/zenoh-plugin-ros2dds

298
C•Moderate(28/100)Rust

A Zenoh plug-in for ROS2 with a DDS RMW. See https://discourse.ros.org/t/ros-2-alternative-middleware-report/ for the advantages of using this plugin over other DDS RMW implementations.

Compare•
Jump to:
Response Velocity
4 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
18.2%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
18.2%
Merge Gauge
50.0%
1st-Timer
Community Vibe22/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for eclipse-zenoh/zenoh-plugin-ros2dds
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/eclipse-zenoh/zenoh-plugin-ros2dds)](https://getmerged.abhishekco.de/eclipse-zenoh/zenoh-plugin-ros2dds?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for eclipse-zenoh/zenoh-plugin-ros2dds.

View all good first issues directly on GitHub

Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for eclipse-zenoh/zenoh-plugin-ros2dds

When evaluating whether to contribute to eclipse-zenoh/zenoh-plugin-ros2dds, 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 eclipse-zenoh/zenoh-plugin-ros2dds acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 18.2% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to eclipse-zenoh/zenoh-plugin-ros2dds

01

Is eclipse-zenoh/zenoh-plugin-ros2dds welcoming to first-time open-source contributors?

eclipse-zenoh/zenoh-plugin-ros2dds has a recorded first-timer success rate of 50.0%. Repositories ranked Moderate typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~4 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 28.5 C-Rankâ„¢ score represent?

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 28.5 places eclipse-zenoh/zenoh-plugin-ros2dds in the Moderate tier.

04

What is the external contributor pull request merge rate for eclipse-zenoh/zenoh-plugin-ros2dds?

The external pull request merge rate is 18.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in eclipse-zenoh/zenoh-plugin-ros2dds?

eclipse-zenoh/zenoh-plugin-ros2dds does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rankâ„¢ Indexing Standard

All metrics displayed for eclipse-zenoh/zenoh-plugin-ros2dds 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.