Overte open source virtual worlds platform.
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 50%
Response Time: 12h
First Timer Success: -
overte-org/overte 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 overte-org/overte respond to incoming external pull requests in approximately 12.3 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 52.6 places overte-org/overte in the B tier.
The external contributor pull request merge rate for overte-org/overte is 50.0%, based on public PR activity from non-core contributors.
overte-org/overte currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in overte-org/overte. Reviews community pull requests with focus on project quality.
Discussions in overte-org/overte focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/overte-org/overte?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (62% approval). Large PRs (>500 lines) take ~59 hours (22% approval). Keep your diff compact for rapid review.
This is a weird one, the error somehow went away while trying to debug it! Crash happened after a long time of uneventful running under ASAN/UBSAN. It crashed when I clicked the "People" button, before anything showed up. Thread 119 "qrc:///qml/hifi" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7bfe9bfff6c0 (LWP 275488)] 0x00007bff843831ea in _mesa_check_shared_resource_usage (ctx=0x7bfee12ac800, resource=0x7d5fa2981a80, only_user=<synthetic pointer>) at ../src/mesa/main/shared.c:477 477 bool is_busy = threaded_context_is_buffer_on_busy_list(shared_ctx->st->pipe, resource); (gdb) p $_siginfo._sifields._sigfault.si_addr $4 = (void *) 0x10 So it appears the error is that we're accessing 0x10. Where? (gdb) print shared_ctx $1 = (struct gl_context *) 0x7bfdc37bd800 (gdb) print shared_ctx->st $2 = (struct st_context *) 0x7eefa4604400 (gdb) print shared_ctx->st->pipe $3 = (struct pipe_context *) 0x7bfe07418800 This looks good, and the entire struct is readable:
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 overte-org/overte, 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 overte-org/overte acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
overte-org/overte 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 ~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 52.6 places overte-org/overte in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, overte-org/overte 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 overte-org/overte 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.