📦 eCAL - enhanced Communication Abstraction Layer. A high performance publish-subscribe, client-server cross-plattform middleware.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 77%
Response Time: 2d
First Timer Success: 67%
eclipse-ecal/ecal has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eclipse-ecal/ecal respond to incoming external pull requests in approximately 36.7 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 59.5 places eclipse-ecal/ecal in the A tier.
The external contributor pull request merge rate for eclipse-ecal/ecal is 76.9%, based on public PR activity from non-core contributors.
eclipse-ecal/ecal currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (71% critical review signals). Ensure PRs strictly follow guidelines before requesting review in eclipse-ecal/ecal.
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/eclipse-ecal/ecal?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 07:00 UTC (07: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 ~24 hours (96% approval). Large PRs (>500 lines) take ~176 hours (35% approval). Keep your diff compact for rapid review.
Problem Description Currently, eCAL internally calculates a version number using git describe, and python packaging also computes a version number for it. However, these version numbers don't match under certain conditions. However they are compared in Python unit tests, which leads to failing unit tests. We have to adapt one or the other to achieve matching version numbers. (only true for commits which are not a clean tag). How to reproduce Run eCAL Python unittests e.g. on support/v6.1 Unit test failure output assert version.major == ecal_package_version.major assert version.minor == ecal_package_version.minor > assert version.patch == ecal_package_version.micro E AssertionError: assert 0 == 1 E + where 0 = <Version major=6, minor=1, patch=0>.patch E + and 1 = <Version('6.1.1.dev14+g9217d1f06')>.micro
This consists of multiple steps: Rework ecal timegate to be based on a new Dynamic Library utility in ecal_utils (#2523) Remove old ecaltime-localtime plugin (#2531) Check ecaltime-simtime plugin. remove eTimeSyncMode (as it is always set to replay)
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 eclipse-ecal/ecal, 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-ecal/ecal acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.9% were successfully merged into the primary branch.
eclipse-ecal/ecal has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming 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 59.5 places eclipse-ecal/ecal in the Welcoming tier.
The external pull request merge rate is 76.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eclipse-ecal/ecal 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 eclipse-ecal/ecal 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.